1. 31 5月, 2006 1 次提交
  2. 24 5月, 2006 1 次提交
    • A
      [PATCH] PATCH: libata. Add ->data_xfer method · a6b2c5d4
      Alan Cox 提交于
      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: NAlan Cox <alan@redhat.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      a6b2c5d4
  3. 11 4月, 2006 1 次提交
  4. 03 4月, 2006 1 次提交
  5. 02 4月, 2006 1 次提交
  6. 22 3月, 2006 1 次提交
  7. 21 2月, 2006 1 次提交
  8. 13 2月, 2006 1 次提交
  9. 12 2月, 2006 1 次提交
  10. 10 2月, 2006 1 次提交
  11. 27 1月, 2006 1 次提交
  12. 06 12月, 2005 1 次提交
  13. 01 12月, 2005 1 次提交
  14. 17 11月, 2005 1 次提交
  15. 12 11月, 2005 1 次提交
  16. 11 11月, 2005 1 次提交
  17. 10 11月, 2005 1 次提交
  18. 07 11月, 2005 1 次提交
  19. 31 10月, 2005 1 次提交
  20. 30 10月, 2005 2 次提交
    • J
      [libata] change ata_qc_complete() to take error mask as second arg · a7dac447
      Jeff Garzik 提交于
      The second argument to ata_qc_complete() was being used for two
      purposes: communicate the ATA Status register to the completion
      function, and indicate an error.  On legacy PCI IDE hardware, the latter
      is often implicit in the former.  On more modern hardware, the driver
      often completely emulated a Status register value, passing ATA_ERR as an
      indication that something went wrong.
      
      Now that previous code changes have eliminated the need to use drv_stat
      arg to communicate the ATA Status register value, we can convert it to a
      mask of possible error classes.
      
      This will lead to more flexible error handling in the future.
      a7dac447
    • J
      [libata] ensure ->tf_read() hook reads Status and Error registers · ac19bff2
      Jeff Garzik 提交于
      We want ->tf_read() to get a complete snapshot of all taskfile
      registers, without requiring the callers to manually call
      ata_chk_status() and ata_chk_err() themselves.
      
      This also fixes a minor bug in sata_vsc where the lower bits of the
      feature register were incorrectly placed in the HOB (high order bits)
      portion of struct ata_taskfile.
      ac19bff2
  21. 23 10月, 2005 1 次提交
  22. 21 10月, 2005 1 次提交
    • A
      [PATCH] enum safety (sata_qstor) · 0420dd12
      Al Viro 提交于
      sata_qstor strays into a nasty area - gcc handling of wide enums is
      full of bugs that got fixed between gcc versions creating portability
      nightmare.  Single-member enums are safe, so are ones that stay within
      the range of int or unsigned int.  Anything beyond that is asking for
      trouble.
      
      Declaration of constants split in two enums, taking the ~0UL one into
      a separate enum.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      0420dd12
  23. 05 10月, 2005 1 次提交
  24. 29 9月, 2005 1 次提交
  25. 08 9月, 2005 1 次提交
  26. 30 8月, 2005 1 次提交
  27. 29 8月, 2005 1 次提交
    • J
      [libata] license change, other bits · af36d7f0
      Jeff Garzik 提交于
      - 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
        obtained
      
      - where I have made major contributions, updated copyright dates
      af36d7f0
  28. 27 8月, 2005 2 次提交
  29. 23 8月, 2005 1 次提交
    • T
      [PATCH] fix atapi_packet_task vs. intr race (take 2) · c1389503
      Tejun Heo 提交于
      Interrupts from devices sharing the same IRQ could cause
      ata_host_intr to finish commands being processed by atapi_packet_task
      if the commands are using ATA_PROT_ATAPI_NODATA or ATA_PROT_ATAPI_DMA
      protocol.  This is because libata interrupt handler is unaware that
      interrupts are not expected during that period.  This patch adds
      ATA_FLAG_NOINTR flag to tell the interrupt handler that we're not
      expecting interrupts.
      
       Note that once proper HSM is implemented for interrupt-driven PIO,
      this should be merged into it and this flag will be removed.
      
       ahci.c is a different kind of beast, so it's left alone.
      
      * The following drivers use ata_qc_issue_prot and ata_interrupt, so
        changes in libata core will do.
      
        ata_piix sata_sil sata_svw sata_via sata_sis sata_uli
      
      * The following drivers use ata_qc_issue_prot and custom intr handler.
        They need this change to work correctly.
      
        sata_nv sata_vsc
      
      * The following drivers use custom issue function and intr handler.
        Currently all custom issue functions don't support ATAPI, so this
        change is irrelevant, updated for consistency and to avoid later
        mistakes.
      
        sata_promise sata_qstor sata_sx4
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      c1389503
  30. 01 8月, 2005 1 次提交
  31. 27 5月, 2005 1 次提交
    • J
      libata: Fix use-after-iounmap · aa8f0dc6
      Jeff Garzik 提交于
      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.
      aa8f0dc6
  32. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4