From: Jeff Garzik <jeff@garzik.org>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: PATA drivers queued for 2.6.19
Date: Mon, 04 Sep 2006 07:01:13 -0400 [thread overview]
Message-ID: <44FC0779.9030405@garzik.org> (raw)
I just pulled the "pata-drivers" branch of libata-dev.git into the
"upstream" branch, which means that Alan's libata PATA driver collection
is now queued for 2.6.19.
Testing-wise, these PATA drivers have been Andrew Morton's -mm tree for
many months. Community-wise, no one posted objections to the PATA
driver merge plan, when Alan posted it on LKML and linux-ide.
The following must be in all caps, though:
drivers/ide IS STILL THE PATA DRIVER SET THAT USERS AND DISTROS SHOULD
CHOOSE.
At this time, drivers/ide should not be added to
Documentation/feature-removal-schedule.txt. The libata PATA driver set
should be considered experimental still, and there remains a few
user-visible differences between the two trees:
* Host-protected area (HPA) not ignored in libata, which means disk
sizes differ between drivers/ide (whole disk) and libata (whole disk
minus HPA).
* The obvious change between /dev/hdX to /dev/sdX
* /dev/sdX supports fewer partitions than /dev/hdX (16 versus 64, IIRC)
* /dev/sdX does not support all the HDIO_xxx ioctls that /dev/hdX does.
In practice, the ioctls we ignored are ones that very few people care
about.
* ARM, PPC and other non-x86 platform drivers are severely
under-represented.
As an aside, I would love to see paride updated to use libata, but we
can probably count the number of paride users on one hand these days...
Jeff
--
VGER BF report: U 0.499983
next reply other threads:[~2006-09-04 11:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:01 Jeff Garzik [this message]
2006-09-04 12:02 ` PATA drivers queued for 2.6.19 Grant Coady
2006-09-04 12:07 ` Jan Engelhardt
2006-09-04 12:35 ` Tomasz Torcz
2006-09-04 13:35 ` Jan Engelhardt
2006-09-05 13:26 ` Helge Hafting
2006-09-05 14:39 ` Alan Cox
2006-09-05 16:51 ` Grant Coady
2006-09-05 17:57 ` Krzysztof Halasa
2006-09-05 21:24 ` Grant Coady
2006-09-04 12:12 ` Jeff Garzik
2006-09-04 13:27 ` Alan Cox
2006-09-04 12:02 ` Alan Cox
2006-09-04 12:10 ` Jan Engelhardt
2006-09-04 12:15 ` Jeff Garzik
2006-09-05 13:30 ` John Stoffel
2006-09-05 13:46 ` Sergei Shtylyov
2006-09-05 15:10 ` John Stoffel
2006-09-05 20:48 ` Bill Davidsen
2006-09-06 7:48 ` Alan Cox
2006-09-04 21:31 ` Andras Mantia
2006-09-05 2:25 ` Jeff Garzik
2006-09-21 11:55 ` Lennert Buytenhek
2006-09-22 9:51 ` Jeff Garzik
2007-01-28 20:21 ` cirrus ep93xx pata driver (was: Re: PATA drivers queued for 2.6.19) Lennert Buytenhek
2007-05-29 1:27 ` cirrus ep93xx pata driver Jeff Garzik
2007-05-29 1:48 ` Lennert Buytenhek
2007-05-29 2:58 ` 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=44FC0779.9030405@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).