aboutsummaryrefslogtreecommitdiff
path: root/include/linux/ata.h
AgeCommit message (Collapse)Author
2005-10-22libata: const-ification bombing runJeff Garzik
Enforce access rules where appropriate. If the compiler is smart enough, this may buy us an optimization or two as a side effect.
2005-10-21libata: handle early device PIO modes correctlyAlan Cox
2005-10-18[PATCH] libata CHS: calculate read/write commands and protocol on the fly ↵Albert Lee
(revise #6) - merge ata_prot_to_cmd() and ata_dev_set_protocol() as ata_rwcmd_protocol() - pave road for read/write multiple support - remove usage of pre-cached command and protocol values and call ata_rwcmd_protocol() instead Signed-off-by: Albert Lee <albertcc@tw.ibm.com> ============== Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
2005-09-28[PATCH] ata: re-order speeds sensibly.Alan Cox
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
2005-08-29Merge libata branch 'chs-support' to latest upstream kernel.Jeff Garzik
2005-08-29Merge /spare/repo/linux-2.6/Jeff Garzik
2005-08-28[libata] license change, other bitsJeff Garzik
- 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
2005-08-11[libata scsi] add START STOP UNIT translationDouglas Gilbert
2005-06-22Merge upstream kernel changes into 'C/H/S support' branch of libata.Jeff Garzik
2005-05-12[libata] C/H/S support, for older devicesAlbert Lee
2005-05-12[PATCH] libata basic detection and errata for PATA->SATA bridgesBrad Campbell
This patch works around an issue with WD drives (and possibly others) over SiL PATA->SATA Bridges on SATA controllers locking up with transfers > 200 sectors. Signed-off-by: Brad Campbell <brad@wasp.net.au>
2005-04-16Linux-2.6.12-rc2Linus Torvalds
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!