26 Aug, 2010

1 commit


11 Aug, 2010

1 commit


02 Aug, 2010

2 commits


18 Jun, 2010

1 commit

  • This patch adds a driver for a harddrive attached to PXA address and data bus.
    Unlike pata_platform, this driver allows usage of PXA DMA controller, making the
    transmission speed 3x higher.

    Signed-off-by: Marek Vasut
    Acked-by: Jeff Garzik
    Signed-off-by: Eric Miao

    Marek Vasut
     

03 Jun, 2010

1 commit


26 May, 2010

1 commit

  • Make BMDMA optional depending on new config variable CONFIG_ATA_BMDMA.
    In Kconfig, drivers are grouped into five groups - non-SFF native, SFF
    w/ custom DMA interface, SFF w/ BMDMA, PIO-only SFF, and generic
    fallback / legacy ones. Kconfig and Makefile are reorganized
    according to the groups and ordered alphabetically inside each group.

    ata_ioports.bmdma_addr and ata_port.bmdma_prd[_dma] are put into
    CONFIG_ATA_BMDMA, as are all bmdma related ops, variables and
    functions.

    This increase the binary size slightly when BMDMA is enabled but on
    both native-only and PIO-only configurations the size is slightly
    reduced. Either way, the size difference is insignificant. This
    change is more meaningful to signify the separation between SFF and
    BMDMA and as a tool to verify the separation.

    Signed-off-by: Tejun Heo
    Signed-off-by: Jeff Garzik

    Tejun Heo
     

15 May, 2010

2 commits


02 Mar, 2010

1 commit


24 Dec, 2009

1 commit

  • In March 2008 commit 0ac4a3c2fbbcadc3e96e4dc47d4ae802d66e6f67 ("ACPI: fix
    ATA_ACPI build") made CONFIG_ACPI_DOCK be selected by CONFIG_ATA_ACPI because
    of a build error when CONFIG_ATA_ACPI=y and CONFIG_ACPI_DOCK=m.

    However, in September 2008 commit 898b054f3eec5921320ae8614b5bdd7b07ea5b43
    ("dock: make dock driver not a module") removed the possibility of having
    CONFIG_ACPI_DOCK=m and therefore there is no need for selecting it when
    CONFIG_ATA_ACPI=y.

    This makes the kernel ~5 Kb smaller for people who don't have a dock by
    allowing them to not have ACPI_DOCK compiled-in because of ATA_ACPI=y.

    Signed-off-by: Carlos R. Mafra
    Cc: Shaohua Li
    Signed-off-by: Andrew Morton
    Signed-off-by: Len Brown

    Carlos R. Mafra
     

09 Dec, 2009

2 commits


04 Dec, 2009

1 commit

  • We were never able to get docs for this out of Toshiba for years. Dave
    Barnes produced a NetBSD driver however and from that we can fill in the
    needed tables.

    As we correct the PCI identifiers a bit also update the old ide generic driver
    at the same time so it stays compiling.

    Signed-off-by: Alan Cox
    Signed-off-by: Jeff Garzik

    Alan Cox
     

03 Dec, 2009

2 commits


18 Sep, 2009

1 commit


02 Sep, 2009

2 commits

  • From: Alan Cox

    Signed-off-by: Alan Cox
    Signed-off-by: Jeff Garzik

    Alan Cox
     
  • 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: Robert Hancock
    Signed-off-by: Jeff Garzik

    Robert Hancock
     

23 Jun, 2009

1 commit


31 May, 2009

1 commit


30 Mar, 2009

1 commit


26 Jan, 2009

1 commit


16 Jan, 2009

1 commit

  • Cavium OCTEON processor support was recently merged, so now we have
    this CF driver for your consideration.

    Most OCTEON variants have *no* DMA or interrupt support on the CF
    interface so for these, only PIO is supported. Although if DMA is
    available, we do take advantage of it.

    Signed-off-by: David Daney
    Signed-off-by: Jeff Garzik

    David Daney
     

21 Dec, 2008

1 commit

  • This patch adds MDMA/UDMA support using BestComm for DMA on the MPC5200
    platform. Based heavily on previous work by Freescale (Bernard Kuhn,
    John Rigby) and Domen Puncer.

    With this patch, a SanDisk Extreme IV CF card gets read speeds of
    approximately 26.70 MB/sec.

    Signed-off-by: Tim Yamin
    Signed-off-by: Grant Likely

    Tim Yamin
     

09 Dec, 2008

1 commit


12 Oct, 2008

1 commit


29 Sep, 2008

1 commit


17 Sep, 2008

1 commit


09 Sep, 2008

1 commit

  • 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: Alan Cox
    Signed-off-by: Jeff Garzik

    Alan Cox
     

01 Sep, 2008

1 commit

  • 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: Adrian Bunk
    Signed-off-by: David S. Miller

    Adrian Bunk
     

19 Jun, 2008

1 commit


06 May, 2008

2 commits


29 Apr, 2008

1 commit


18 Apr, 2008

4 commits


18 Mar, 2008

1 commit

  • drivers/ata/libata-acpi.c fails to build

    drivers/built-in.o: In function `ata_acpi_associate':
    (.text+0x7106a): undefined reference to `register_hotplug_dock_device'

    When CONFIG_ATA_ACPI=y and CONFIG_ACPI_DOCK=m
    But if dock is selected from ata_acpi, dock will =y
    when ata_acpi=y, avoiding this problem.

    http://bugzilla.kernel.org/show_bug.cgi?id=10272

    Signed-off-by: Len Brown

    Len Brown