1. 02 3月, 2010 1 次提交
  2. 24 12月, 2009 1 次提交
  3. 09 12月, 2009 1 次提交
  4. 04 12月, 2009 1 次提交
  5. 03 12月, 2009 2 次提交
  6. 18 9月, 2009 1 次提交
  7. 02 9月, 2009 2 次提交
    • A
      [libata] Add pata_rdc driver for RDC ATA devices · 6b406782
      Alan Cox 提交于
      From: Alan Cox <alan@linux.intel.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      6b406782
    • R
      libata: add command name parsing for error output · 6521148c
      Robert Hancock 提交于
      This patch improve libata's output for error/notification messages
      to allow easier comprehension and debugging:
      
      When ATAPI commands issued through the SCSI layer fail, use SCSI
      functions to print the CDB in human-readable form instead of just
      dumping out the CDB in hex.
      
      Print out the name of the failed command (as defined by the ATA
      specification) in error handling output along with the raw register
      contents.
      
      When reporting status of ACPI taskfile commands executed on resume,
      also output the names of the commands being executed (or not) in
      readable form.
      
      Since the extra data for printing command names increases kernel
      size slightly, a config option has been added to allow disabling
      command name output (as well as some of the error register parsing)
      for those highly sensitive to kernel text size.
      Signed-off-by: NRobert Hancock <hancockrwd@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      6521148c
  8. 23 6月, 2009 1 次提交
  9. 31 5月, 2009 1 次提交
  10. 30 3月, 2009 1 次提交
  11. 26 1月, 2009 1 次提交
  12. 16 1月, 2009 1 次提交
  13. 21 12月, 2008 1 次提交
  14. 09 12月, 2008 1 次提交
  15. 29 9月, 2008 1 次提交
  16. 09 9月, 2008 1 次提交
    • A
      ahci, pata_marvell: play nicely together · 5b66c829
      Alan Cox 提交于
      I've been chasing Jeff about this for months.  Jeff added the Marvell
      device identifiers to the ahci driver without making the AHCI driver
      handle the PATA port. This means a lot of users can't use current
      kernels and in most distro cases can't even install.
      
      This has been going on since March 2008 for the 6121 Marvell, and late 2007
      for the 6145!!!
      
      This was all pointed out at the time and repeatedly ignored. Bugs assigned
      to Jeff about this are ignored also.
      
      To quote Jeff in email
      
      > "Just switch the order of 'ahci' and 'pata_marvell' in
      > /etc/modprobe.conf, then use Fedora's tools regenerate the initrd.
      
      > See?  It's not rocket science, and the current configuration can be
      > easily made to work for Fedora users."
      
      (Which isn't trivial, isn't end user, shouldn't be needed, and as it usually
      breaks at install time is in fact impossible)
      
      To quote Jeff in August 2007
      
      > "   mv-ahci-pata
      > Marvell 6121/6141 PATA support.  Needs fixing in the 'PATA controller
      > command' area before it is usable, and can go upstream."
      
      Only he add the ids anyway later and caused regressions, adding a further
      id in March causing more regresions.
      
      The actual fix for the moment is very simple. If the user has included
      the pata_marvell driver let it drive the ports. If they've only selected
      for SATA support give them the AHCI driver which will run the port a fraction
      faster. Allow the user to control this decision via ahci.marvell_enable as
      a module parameter so that distributions can ship 'it works' defaults and
      smarter users (or config tools) can then flip it over it desired.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      5b66c829
  17. 01 9月, 2008 1 次提交
    • A
      sparc: remove CONFIG_SUN4 · 5110bd21
      Adrian Bunk 提交于
      While doing some easy cleanups on the sparc code I noticed that the
      CONFIG_SUN4 code seems to be worse than the rest - there were some
      "I don't know how it should work, but the current code definitely cannot
      work." places.
      
      And while I have seen people running Linux on machines like a
      SPARCstation 5 a few years ago I don't recall having seen sun4
      machines, even less ones running Linux.
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5110bd21
  18. 19 6月, 2008 1 次提交
  19. 06 5月, 2008 2 次提交
  20. 29 4月, 2008 1 次提交
  21. 18 4月, 2008 4 次提交
  22. 18 3月, 2008 1 次提交
  23. 11 3月, 2008 1 次提交
  24. 02 2月, 2008 1 次提交
  25. 28 1月, 2008 1 次提交
  26. 23 1月, 2008 1 次提交
  27. 16 1月, 2008 1 次提交
  28. 18 10月, 2007 2 次提交
  29. 16 10月, 2007 1 次提交
  30. 13 10月, 2007 4 次提交
    • A
      pata_acpi: ACPI driver support · 025621f9
      Alan Cox 提交于
      	On a cable there may be
      	eighty wires or perhaps forty
      	and we learn about its type
      	In the world of ACPI
      
      	So we call the GTM
      	And we find the the timing rate
      	And we look through it to see
      	If eighty wire it must be
      
      	Timing lives in ACPI routines
      	ACPI routines, ACPI routines
      	Timing lives in ACPI routines
      	ACPI routes ACPI routines
      
      	And the drivers last you see
      	Picking up unknown pci ids
      	and the code begins to work
      
      	Timing lives in ACPI routines
      	ACPI routines, ACPI routines
      	Timing lives in ACPI routines
      	ACPI routes ACPI routines
      
      	[Full speed ahead, Mr Hacker, full speed ahead]
      	 Full speed over here sir!
      	 Checking Cable, checking cable
      	 Aye aye, 80 wire,
      	 Heaven heaven]
      
      	If we use ACPI (ACPI)
      	Every box (every box) has all we need (has all we need)
      	Cable type (cable type) and mode timing (mode timing)
      	In our ATA (in our ATA) subroutines (subroutines, ha ha)
      
      	Timing lives in ACPI routines
      	ACPI routines, ACPI routines
      	Timing lives in ACPI routines
      	ACPI routes ACPI routines
      	Timing lives in ACPI routines
      	ACPI routines, ACPI routines
      	Timing lives in ACPI routines
      	ACPI routes ACPI routines
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      025621f9
    • A
      pata_ns87415: Initial cut at 87415/87560 IDE support · c4b5b7b6
      Alan Cox 提交于
      Signed-off-by: NAlan Cox <alan@redhat.com>
      [plus SuperIO fixes by Kyle McMartin]
      [plus a cleanup from me]
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      c4b5b7b6
    • A
      libata: Update experimental tags to reflect reality better · c645fd34
      Alan Cox 提交于
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      c645fd34
    • K
      AVR32 PATA driver · 7c9ef8e4
      Kristoffer Nyborg Gregertsen 提交于
      Updated and simplified driver. Use only register transfer timing for both
      data and register transfers. This gives poorer performance in PIO1 and 2,
      but should not be a problem in PIO3 and 4, correct me if I'm wrong :)
      
      The driver works very we'll but I still wonder about the interrupts. I have
      an interrupt line, that works nicely when POLLING flag is not set. The
      problem is the number of interrupts that eat away my CPU cycles.
      
      When using the POLLING flag there seem to be some interrupts that dosen't get
      cleared. Furthermore the device dosen't drive INTRQ high, it stays at 2.5 volts
      and generates a lot of interrupts due to ripple / noise. What to do?
      Signed-off-by: NKristoffer Nyborg Gregertsen <kngregertsen@norway.atmel.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      7c9ef8e4