1. 28 9月, 2006 1 次提交
  2. 26 9月, 2006 1 次提交
  3. 24 8月, 2006 1 次提交
    • J
      libata: Grand renaming. · cca3974e
      Jeff Garzik 提交于
      The biggest change is that ata_host_set is renamed to ata_host.
      
      * ata_host_set			=> ata_host
      * ata_probe_ent->host_flags	=> ata_probe_ent->port_flags
      * ata_probe_ent->host_set_flags	=> ata_probe_ent->_host_flags
      * ata_host_stats		=> ata_port_stats
      * ata_port->host		=> ata_port->scsi_host
      * ata_port->host_set		=> ata_port->host
      * ata_port_info->host_flags	=> ata_port_info->flags
      * ata_(.*)host_set(.*)\(\)	=> ata_\1host\2()
      
      The leading underscore in ata_probe_ent->_host_flags is to avoid
      reusing ->host_flags for different purpose.  Currently, the only user
      of the field is libata-bmdma.c and probe_ent itself is scheduled to be
      removed.
      
      ata_port->host is reused for different purpose but this field is used
      inside libata core proper and of different type.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      cca3974e
  4. 10 8月, 2006 2 次提交
  5. 01 7月, 2006 1 次提交
  6. 27 6月, 2006 1 次提交
  7. 23 6月, 2006 1 次提交
  8. 20 6月, 2006 7 次提交
  9. 31 5月, 2006 1 次提交
  10. 24 5月, 2006 2 次提交
  11. 11 4月, 2006 1 次提交
  12. 03 4月, 2006 1 次提交
  13. 02 4月, 2006 1 次提交
  14. 23 3月, 2006 2 次提交
  15. 22 3月, 2006 1 次提交
  16. 13 2月, 2006 1 次提交
  17. 10 2月, 2006 1 次提交
  18. 09 1月, 2006 1 次提交
    • A
      [PATCH] sata_nv, spurious interrupts at system startup with MAXTOR 6H500F0 drive · b887030a
      Andrew Chew 提交于
      This patch works around a problem with spurious interrupts seen at boot time when
      a MAXTOR 6H500F0 drive is present.  An ATA interrupt condition is mysteriously
      present at start of day.  If we took too long in issuing the first command,
      the kernel would basically get tired of the spurious interrupts and turn the interrupt
      off.  Issuing the first command essentially causes the interrupt condition to
      get acknowledged.
      
      I haven't seen this happen with any other drives.
      
      What I basically do is ack ATA status by reading it regardless of whether we're
      expecting to have to handle an interrupt.  This clears the start-of-day anomalous
      interrupt condition, and keeps the kernel from disabling that interrupt due to
      too many spurious interrupts.
      
      Also, I fixed a bug where hotplug interrupts weren't getting acknowledged as handled
      in the ISR.  This was not the cause of the spurious interrupts, but it's the right
      thing to do anyway.
      
      Signed-Off-By: Andrew Chew
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      b887030a
  19. 06 1月, 2006 1 次提交
  20. 11 11月, 2005 1 次提交
  21. 10 11月, 2005 1 次提交
  22. 07 11月, 2005 1 次提交
  23. 31 10月, 2005 1 次提交
  24. 23 10月, 2005 1 次提交
  25. 21 10月, 2005 1 次提交
  26. 11 10月, 2005 1 次提交
  27. 09 10月, 2005 1 次提交
  28. 04 10月, 2005 1 次提交
    • A
      libata: bitmask based pci init functions for one or two ports · 47a86593
      Alan Cox 提交于
      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)
      47a86593
  29. 29 9月, 2005 1 次提交
  30. 22 9月, 2005 1 次提交
  31. 30 8月, 2005 1 次提交