From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Libata PATA status
Date: Thu, 05 Jul 2007 19:25:08 -0400 [thread overview]
Message-ID: <468D7DD4.9060306@garzik.org> (raw)
In-Reply-To: <p73k5tg2uj9.fsf@bingen.suse.de>
Andi Kleen wrote:
> My personal wish list feature would be a little forwarder driver
> to forward /dev/hd* to /dev/sd* for this; then old IDE could be
> disabled without risking breaking old root file systems.
That's on the long-term TODO list.
libata is moving towards making libata-scsi an optional module (will
always be around for ATAPI, and for compat with current ATA), and
driving ATA disks as a native block driver, rather than having SCSI do
the work for us.
libata's qc_issue/qc_complete high level API and internal modularity
were designed to make this possible. It is easy to see in the current
code how libata-scsi is merely a user of the qc_issue/qc_complete API,
with all the low-level details isolated away from that module.
Addendum: Remember too, /dev/hdX is not just a major/minor pair, but a
userspace interface, complete with expected ioctl support.
Jeff
next prev parent reply other threads:[~2007-07-05 23:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 17:51 Alan Cox
2007-07-04 3:04 ` Kyle Moffett
2007-07-04 9:21 ` Alan Cox
2007-07-04 11:31 ` Marc Dietrich
2007-07-04 12:10 ` Alan Cox
2007-07-04 14:18 ` Marc Dietrich
[not found] ` <20070705183355.187e96bc@the-village.bc.nu>
2007-07-06 8:58 ` Marc Dietrich
2007-07-04 13:00 ` Andi Kleen
2007-07-04 12:17 ` Alan Cox
2007-07-04 13:02 ` Andi Kleen
2007-07-04 13:18 ` Alan Cox
2007-07-04 13:29 ` Andi Kleen
2007-07-04 14:23 ` Alan Cox
2007-07-04 12:19 ` Alan Cox
2007-07-05 23:25 ` Jeff Garzik [this message]
2007-07-05 22:27 ` Rod Whitby
2007-07-06 9:48 ` Libata PATA status (pata_artop) Michael-Luke Jones
2007-07-04 9:17 Libata PATA status Mikael Pettersson
2007-07-05 8:18 Chris Rankin
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=468D7DD4.9060306@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--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
Powered by JetHome