summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/sata_uli.c
Commit message (Collapse)AuthorAgeFilesLines
* [BLOCK] update libata to use new blk_ordered for barriersTejun Heo2006-01-061-1/+0Star
| | | | | | | | Reflect changes in SCSI midlayer and updated to use new ordered request implementation Signed-off-by: Tejun Heo <htejun@gmail.com> Signed-off-by: Jens Axboe <axboe@suse.de>
* [libata] constify PCI ID table in several driversJeff Garzik2005-11-101-1/+1
|
* [libata] eliminate use of drivers/scsi/scsi.h compatibility header/definesJeff Garzik2005-11-071-2/+1Star
|
* [libata] use dev_printk() throughout driversJeff Garzik2005-10-301-0/+5
| | | | | | A few drivers were not following the standard meme of printing out their driver name and version at module load time; this is fixed as well.
* libata: const-ification bombing runJeff Garzik2005-10-221-1/+1
| | | | | | | Enforce access rules where appropriate. If the compiler is smart enough, this may buy us an optimization or two as a side effect.
* libata: bitmask based pci init functions for one or two portsAlan Cox2005-10-041-1/+1
| | | | | | | | | | | | | | 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)
* [PATCH] PCI/libata INTx cleanupBrett M Russ2005-09-091-13/+1Star
| | | | | | | | | Simple cleanup to eliminate X copies of the pci_enable_intx() function in libata. Moved ahci.c's pci_intx() to pci.c and use it throughout libata and msi.c. Signed-off-by: Brett Russ <russb@emc.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* [PATCH] libata: fix pio_mask values (take 2)Brett Russ2005-09-071-2/+2
| | | | | | | | | | | | | | ata_get_mode_mask() uses bits 3 and 4 in the pio_mask to represent PIO modes 3 and 4. The value read from the drive, which reports support for PIO3 and PIO4 in bits 0 and 1, is shifted left by 3 bits and OR'd with 0x7 (which then corresponds to PIO 2-0 in libata). Thus, the drivers below need adjustments to comply with the way pio_mask is used. I changed the masks from the commented values to all support PIO4-0, since the spec mandates that PIO0-2 are supported and there's no reason not to support PIO3 IMO. Signed-off-by: Brett Russ <russb@emc.com> Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
* Merge /spare/repo/linux-2.6/Jeff Garzik2005-08-291-1/+1
|\
| * libata: trim trailing whitespace.Jeff Garzik2005-07-311-1/+1
| | | | | | | | Also, fixup a tabs-to-spaces block of code in ata_piix.
* | [libata] license change, other bitsJeff Garzik2005-08-291-14/+19
|/ | | | | | | | | | | - 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
* libata: Fix use-after-iounmapJeff Garzik2005-05-271-0/+1
| | | | | | | | | | | | | | | | | | 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.
* Linux-2.6.12-rc2Linus Torvalds2005-04-171-0/+287
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!