From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Chew <achew@nvidia.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
B.Zolnierkiewicz@elka.pw.edu.pl,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: IDE class driver with SATA controllers
Date: Wed, 01 Sep 2004 09:19:42 -0400 [thread overview]
Message-ID: <4135CC6E.3050508@pobox.com> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B03F969B@hqemmail02.nvidia.com>
Andrew Chew wrote:
> The reason I'm asking is because it would seem like a good thing to have
> SATA controllers that are broadly compatible with IDE to be usable
> without having to modify the core kernel drivers. This would at least
> allow a user to perform a Linux install on a SATA drive even if that
> kernel doesn't have explicit support for the SATA controller. A
> kernel/driver update can then take place after the install.
>
> Also, are there plans for libata to take over the IDE class driver
> functionality in the future?
Once ATAPI is complete, then I will green-light PATA support in libata.
Since libata already supports the standard bmdma stuff, and can even
work in PIO-only mode without DMA (or even without interrupts, in 100%
polling mode), it is definitely possible to drive the hardware.
If you want to play, and don't care about lack of ATAPI support (i.e.
just disks), then it is possible today to do this. #define
ATA_FORCE_PIO and play away :)
With regards to libata being the default, making that an _option_ is
feasible, but we will probably default to the IDE driver for quite some
time. There are issues of /dev/hda versus /dev/sda, keeping existing
user setups working, etc.
Jeff
next prev parent reply other threads:[~2004-09-01 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 21:03 IDE class driver with SATA controllers Andrew Chew
2004-09-01 12:01 ` Alan Cox
2004-09-01 13:19 ` Jeff Garzik [this message]
2004-09-01 15:45 ` Julien Oster
-- strict thread matches above, loose matches on Subject: below --
2004-09-08 0:21 Andrew Chew
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=4135CC6E.3050508@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=achew@nvidia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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).