From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: libata-dev queue updated
Date: Thu, 2 Dec 2004 03:29:30 -0500 [thread overview]
Message-ID: <20041202082930.GA7512@havoc.gtf.org> (raw)
I just updated libata-dev queue in BitKeeper, to the latest upstream kernel.
No patch yet, I'll post in a day or two. You can generate your own
patch using Documentation/BK-usage/gcapatch script in the kernel tree.
Here's a summary of the stuff sitting in this testing queue:
* new driver ata_adma (Pacific Digital PATA and SATA)
* new hardware ULi 5281 supported in sata_uli driver
* new hardware VT6421 SATA supported in sata_via driver
* support for PATA ports on Promise SATA cards
* support for newer Promise PATA cards
* ATA passthru (read: SMART support)
* other minor stuff
BK users:
bk pull bk://gkernel.bkbits.net/libata-dev-2.6
This will update the following files:
Documentation/DocBook/libata.tmpl | 192 ++++++++++
drivers/scsi/Kconfig | 18
drivers/scsi/Makefile | 2
drivers/scsi/ahci.c | 5
drivers/scsi/ata_adma.c | 636 ++++++++++++++++++++++++++++++++++
drivers/scsi/libata-core.c | 48 ++
drivers/scsi/libata-scsi.c | 413 ++++++++++++++++++++++
drivers/scsi/libata.h | 2
drivers/scsi/pata_pdc2027x.c | 694 ++++++++++++++++++++++++++++++++++++++
drivers/scsi/sata_promise.c | 56 ++-
drivers/scsi/sata_uli.c | 51 +-
drivers/scsi/sata_via.c | 202 ++++++++---
include/linux/ata.h | 1
include/linux/libata.h | 2
include/scsi/scsi.h | 3
15 files changed, 2221 insertions(+), 104 deletions(-)
through these ChangeSets:
<albertcc:tw.ibm.com>:
o [libata pdc2027x] fix incorrect pio and mwdma masks
o [libata pdc2027x] remove quirks and ROM enable
o [libata] add driver for Promise PATA 2027x
<andyw:pobox.com>:
o [libata scsi] support 12-byte passthru CDB
o [libata scsi] passthru CDB check condition processing
o T10/04-262 ATA pass thru - patch
<erikbenada:yahoo.ca>:
o [libata sata_promise] support PATA ports on SATA controllers
Brad Campbell:
o libata basic detection and errata for PATA->SATA bridges
Jeff Garzik:
o [libata docs] add chapter on libata driver API
o [libata] add new driver ata_adma
o [libata ahci] minor fixes
o [libata sata_uli] add 5281 support, fix SATA phy setup for others
o [libata sata_via] add support for VT6421 SATA
o [libata sata_via] minor cleanups
o [libata] fix DocBook bugs
o [libata pdc2027x] update for upstream struct device conversion
o [libata sata_promise] fix merge bugs
o [libata] fix build breakage
o [libata] fix SATA->PATA bridge detect compile breakage
o [libata] fix printk warning
John W. Linville:
o libata: SMART support via ATA pass-thru
Tobias Lorenz:
o libata-scsi: get-identity ioctl support
next reply other threads:[~2004-12-02 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 8:29 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 7:10 libata-dev queue updated Jeff Garzik
2005-08-24 6:56 Jeff Garzik
2005-08-25 6:56 Tomita, Haruo
2005-08-25 11:02 ` Adrian Bunk
2005-08-26 0:04 Tomita, Haruo
[not found] <BF571719A4041A478005EF3F08EA6DF001617B39@pcsmail03.pcs.pc.ome.toshiba.co.jp>
2005-08-26 0:16 ` Adrian Bunk
2005-08-26 8:41 Tomita, Haruo
2006-01-27 13:54 Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041202082930.GA7512@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).