1. 11 Sep, 2006 1 commit
  2. 24 Aug, 2006 1 commit
  3. 02 Jul, 2006 1 commit
  4. 27 Jun, 2006 1 commit
  5. 26 Jun, 2006 1 commit
  6. 20 Jun, 2006 1 commit
    • Tejun Heo's avatar
      [PATCH] sata_via: convert to new EH, take #3 · 40ef1d8d
      Tejun Heo authored
      Convert sata_via to new EH.  vt6420 used ATA_FLAG_SRST while vt6421
      used ATA_FLAG_SATA_RESET.  This difference seems to be an accident
      rather than intended.  This patch makes both flavors use
      ata_bmdma_error_handler() which makes use of both SRST and SATA
      hardreset.  This behavior change is intended and if it breaks
      anything, it should be very easy to spot.
      Signed-off-by: default avatarTejun Heo <htejun@gmail.com>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
  7. 31 May, 2006 1 commit
  8. 23 May, 2006 1 commit
    • Alan Cox's avatar
      [PATCH] PATCH: libata. Add ->data_xfer method · a6b2c5d4
      Alan Cox authored
      We need to pass the device in order to do per device checks such as
      32bit I/O enables. With the changes to include dev->ap we now don't have
      to add parameters however just clean them up. Also add data_xfer methods
      to the existing drivers except ata_piix (which is in the other block of
      patches). If you reject the piix one just add a data_xfer to it...
      Signed-off-by: default avatarAlan Cox <alan@redhat.com>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
  9. 10 Apr, 2006 1 commit
  10. 02 Apr, 2006 1 commit
  11. 21 Mar, 2006 1 commit
  12. 12 Feb, 2006 1 commit
  13. 10 Feb, 2006 1 commit
  14. 06 Jan, 2006 1 commit
  15. 10 Nov, 2005 1 commit
  16. 09 Nov, 2005 1 commit
  17. 06 Nov, 2005 1 commit
  18. 30 Oct, 2005 1 commit
  19. 22 Oct, 2005 1 commit
  20. 04 Oct, 2005 1 commit
    • Alan Cox's avatar
      libata: bitmask based pci init functions for one or two ports · 47a86593
      Alan Cox authored
      This redoes the n_ports logic I proposed before as a bitmask.
      ata_pci_init_native_mode is now used with a mask allowing for mixed mode
      stuff later on. ata_pci_init_legacy_port is called with port number and
      does one port now not two. Instead it is called twice by the ata init
      logic which cleans both of them up.
      There are stil limits in the original code left over
      - IRQ/port mapping for legacy mode should be arch specific values
      - You can have one legacy mode IDE adapter per PCI root bridge on some systems
      - Doesn't handle mixed mode devices yet (but is now a lot closer to it)
  21. 28 Aug, 2005 1 commit
    • Jeff Garzik's avatar
      [libata] license change, other bits · af36d7f0
      Jeff Garzik authored
      - changes license of all code from OSL+GPL to plain ole GPL
        - except for NVIDIA, who hasn't yet responded about sata_nv
        - copyright holders were already contacted privately
      - adds info in each driver about where hardware/protocol docs may be
      - where I have made major contributions, updated copyright dates
  22. 31 Jul, 2005 1 commit
  23. 26 May, 2005 1 commit
    • Jeff Garzik's avatar
      libata: Fix use-after-iounmap · aa8f0dc6
      Jeff Garzik authored
      Jens Axboe pointed out that the iounmap() call in libata was occurring
      too early, and some drivers (ahci, probably others) were using ioremap'd
      memory after it had been unmapped.
      The patch should address that problem by way of improving the libata
      driver API:
      * move ->host_stop() call after all ->port_stop() calls have occurred.
      * create default helper function ata_host_stop(), and move iounmap()
      call there.
      * add ->host_stop_prewalk() hook, use it in sata_qstor.c (hi Mark).
      sata_qstor appears to require the host-stop-before-port-stop ordering
      that existed prior to applying the attached patch.
  24. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!