From: Jeff Garzik <jeff@garzik.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Woodhouse <dwmw2@infradead.org>,
Adrian Bunk <bunk@stusta.de>,
bzolnier@gmail.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] schedule BLK_DEV_IDE_SATA for removal
Date: Sat, 23 Jun 2007 00:20:29 -0400 [thread overview]
Message-ID: <467C9F8D.8020000@garzik.org> (raw)
In-Reply-To: <18044.39404.380472.887065@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Alan Cox writes:
>
>> On Fri, 22 Jun 2007 11:39:45 +0800
>> David Woodhouse <dwmw2@infradead.org> wrote:
>>
>>> On Fri, 2007-06-22 at 01:52 +0200, Adrian Bunk wrote:
>>>> Users should use the libata based drivers for SATA drives.
>>> NAK. Not all IDE drivers are converted yet. Not even all the relatively
>>> common ones.
>> All the common SATA ones are. Just the PowerPC people are falling behind.
>> Really we should obsolete powerpc instead ;)
>
> What SATA drive uses a non-libata driver on PowerPC? In fact the
> sata_svw driver used for SATA drives on G5s was one of the early
> libata drivers. Or are you talking about PATA?
This entire thread is confused :)
Going back to $subject, it is relevant only to the scant few old-IDE
drivers that do indeed successfully probe and talk to SATA drives, from
SATA controllers.
The vast majority have always used libata for SATA, but another option
did indeed exist before libata appeared, for a few controllers.
Alan was just having a bit of fun at dwmw2's expense, since we do indeed
want to see libata drivers for PowerPC PATA as well :)
Jeff
next prev parent reply other threads:[~2007-06-23 4:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 23:52 [RFC: 2.6 patch] schedule BLK_DEV_IDE_SATA for removal Adrian Bunk
2007-06-22 3:39 ` David Woodhouse
2007-06-22 3:42 ` David Woodhouse
2007-06-22 9:10 ` Alan Cox
2007-06-23 3:56 ` Paul Mackerras
2007-06-23 4:20 ` Jeff Garzik [this message]
2007-06-22 9:02 ` Alan Cox
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=467C9F8D.8020000@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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