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
     

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
     

11 Mar, 2008

1 commit


02 Feb, 2008

1 commit

  • The integrated SATA controller is connected directly to the SoC's
    internal bus, not via PCI interface. this patch removes the dependency
    on the PCI interface.

    Signed-off-by: Saeed Bishara
    Signed-off-by: Jeff Garzik

    Saeed Bishara
     

31 Jan, 2008

1 commit


28 Jan, 2008

1 commit


23 Jan, 2008

1 commit

  • Lots of work needed to bring it up to scratch but it does work so you can
    now use the card. That makes it at least useful, especially as the other
    cardbus cards are usually INIC162x which aren't yet supported well.

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

    Alan Cox
     

16 Jan, 2008

1 commit


18 Oct, 2007

2 commits


16 Oct, 2007

1 commit

  • This is a driver for the ATA controller on the Geode CS5536 companion
    chip. The PCI device ID for this device was previously claimed by
    pata_amd.c but the PIO timings were not correct. This driver also
    works around a bug in some BIOSes that handle unaligned access to the
    PCI config registers poorly. Finally, the driver allows fallback to
    using MSR registers for configuration on BIOSes that are truly
    broken.

    Signed-off-by: Martin K. Petersen
    Signed-off-by: Jeff Garzik

    Martin K. Petersen
     

13 Oct, 2007

5 commits

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

    Alan Cox
     
  • Signed-off-by: Alan Cox
    [plus SuperIO fixes by Kyle McMartin]
    [plus a cleanup from me]
    Signed-off-by: Jeff Garzik

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

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

    Kristoffer Nyborg Gregertsen
     
  • Fix all issues pointed out in Jeff's email.

    Acked-by: Alan Cox
    Signed-off-by: Sonic Zhang
    Signed-off-by: Jeff Garzik

    Sonic Zhang
     

11 Jul, 2007

1 commit

  • The HPT343/345 (aka 363) is a bit of a warped device. For many setups you
    need to access the other registers via BAR4 offsets. PIO is now rock
    solid, DMA isn't. Unfortunately the drivers/ide hpt34x driver is
    completely broken so doesn't help further debug.

    Signed-off-by: Alan Cox
    Cc: Bartlomiej Zolnierkiewicz
    Signed-off-by: Andrew Morton
    Signed-off-by: Jeff Garzik

    Alan Cox
     

02 Jul, 2007

1 commit

  • On Mon, 11 Jun 2007 20:28:16 +0200 api wrote:

    > Good day,
    > When doing make menuconfig one comes across CONFIG_BLK_DEV_SD.
    > The help file states that this is for scsi disks.NO MENTION IS MADE THAT
    > IT IS NEEDE FOR SATA DISKS AS WELL!
    > Would have saved me a lot of time if the help was up to date.
    > I hope this can be changed so others can make a kernel for sata systems
    > quicker.

    From: Randy Dunlap

    Add help info for BLK_DEV_SD referring to its use in
    SATA or PATA driver configurations.

    Add help text for "ATA" indicating that it probably needs
    some SCSI config symbols enabled in order to be useful.

    Signed-off-by: Randy Dunlap
    Signed-off-by: Jeff Garzik

    Randy Dunlap
     

05 Jun, 2007

1 commit


04 Jun, 2007

1 commit


22 May, 2007

1 commit


12 May, 2007

2 commits


10 May, 2007

1 commit


09 May, 2007

1 commit


07 May, 2007

1 commit

  • * 'for-linus' of master.kernel.org:/home/rmk/linux-2.6-arm: (82 commits)
    [ARM] Add comments marking in-use ptrace numbers
    [ARM] Move syscall saving out of the way of utrace
    [ARM] 4360/1: S3C24XX: regs-udc.h remove unused macro
    [ARM] 4358/1: S3C24XX: mach-qt2410.c: remove linux/mmc/protocol.h header
    [ARM] mm 10: allow memory type to be specified with ioremap
    [ARM] mm 9: add additional device memory types
    [ARM] mm 8: define mem_types table L1 bit 4 to be for ARMv6
    [ARM] iop: add missing parens in macro
    [ARM] mm 7: remove duplicated __ioremap() prototypes
    ARM: OMAP: fix OMAP1 mpuio suspend/resume oops
    ARM: OMAP: MPUIO wake updates
    ARM: OMAP: speed up gpio irq handling
    ARM: OMAP: plat-omap changes for 2430 SDP
    ARM: OMAP: gpio object shrinkage, cleanup
    ARM: OMAP: /sys/kernel/debug/omap_gpio
    ARM: OMAP: Implement workaround for GPIO wakeup bug in OMAP2420 silicon
    ARM: OMAP: Enable 24xx GPIO autoidling
    [ARM] 4318/2: DSM-G600 Board Support
    [ARM] 4227/1: minor head.S fixups
    [ARM] 4328/1: Move i.MX UART regs to driver
    ...

    Linus Torvalds
     

03 May, 2007

2 commits


29 Apr, 2007

3 commits

  • Both old-IDE and libata should be able handle all controllers and
    devices found using normal resource reservation methods.

    This eliminates the awful, low-performing split-driver configuration
    where old-IDE drove the PATA portion of a PCI device, in PIO-only mode,
    and libata drove the SATA portion of the /same/ PCI device, in DMA mode.
    Typically vendors would ship SATA hard drive / PATA optical
    configuration, which would lend itself to slow (PIO-only) CD-ROM
    performance.

    For Intel users running in combined mode, it is now wholly dependent on
    your driver choice (potentially link order, if you compile both drivers
    in) whether old-IDE or libata will drive your hardware.

    In either case, you will get full performance from both SATA and PATA
    ports now, without having to pass a kernel command line parameter.

    Signed-off-by: Jeff Garzik

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

    Alan Cox
     
  • Support for the PCI CMD640 (not VLB)

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

    Alan Cox
     

19 Mar, 2007

1 commit