From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>
Subject: libata driver update posted
Date: Thu, 17 Jul 2003 17:14:48 -0400 [thread overview]
Message-ID: <3F1711C8.6040207@pobox.com> (raw)
Just updated libata library and associated ata_piix driver with several
bug fixes and internal improvements. It now works in 2.6 (again).
Next update will add several host drivers, now that the libata API is
settling down.
2.4.21-based patch:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.4/2.4.21-libata4.patch.bz2
2.4.21-based BitKeeper repo:
bk://kernel.bkbits.net/jgarzik/atascsi-2.4
2.6.0-test1-based patch:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.0-test1-libata1.patch.bz2
2.6.0-test1-based BitKeeper repo:
bk://kernel.bkbits.net/jgarzik/atascsi-2.5
(yes, "2.5" is not a typo, I haven't changed the name to 2.6 yet)
Remove the ".??" if the file has not appeared on your favorite
kernel.org mirror yet.
Changes:
* beginnings of pluggable timing configuration
* beginnings of cable detection
* much improved ATA device probing
* a bunch of internal improvements and cleanups (too many to list)
* additional of DocBook documentation
* many bug fixes
next reply other threads:[~2003-07-17 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 21:14 Jeff Garzik [this message]
2003-07-18 6:24 ` libata driver update posted Catalin BOIE
2003-07-18 13:13 ` Jeff Garzik
2003-07-18 15:39 ` Martin Schlemmer
2003-07-18 15:43 ` Jeff Garzik
2003-07-19 0:30 ` Martin Schlemmer
2003-07-19 0:38 ` Alan Cox
2003-07-19 0:52 ` Martin Schlemmer
2003-07-19 0:45 ` Andre Tomt
2003-07-19 0:45 ` Andre Tomt
2003-07-19 20:08 ` Martin Schlemmer
2003-07-19 20:13 ` Jeff Garzik
2003-07-19 21:18 ` Martin Schlemmer
2003-07-20 2:27 ` James H. Cloos Jr.
2003-07-20 2:51 ` 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=3F1711C8.6040207@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.