From: Arjan van de Ven <arjanv@redhat.com>
To: john@grabjohn.com
Cc: rmk@arm.linux.org.uk, jgarzik@pobox.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFR] a new SCSI driver
Date: 25 May 2003 12:45:25 +0200 [thread overview]
Message-ID: <1053859525.1571.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200305251119.h4PBJOal000678@81-2-122-30.bradfords.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Sun, 2003-05-25 at 13:19, john@grabjohn.com wrote:
> > > Thinking ahead, by the 2.8 timescale, PATA could well be legacy hardware
> > > which could be supported only by an 'old' IDE driver, much like we already
> > > have at the moment - I.E. we could remove the current 'old' IDE driver
> > > sometime during the 2.7 timescale, and support SATA only via the SCSI layer.
>
> > Rubbish. PIO mode ATA will be around for some years to come - there
> > is just too much invested there (especially in the embedded world) for
> > it to vanish this quickly. For example, think about compact flash cards,
> > many of which are still driven using PIO mode accesses in todays PDAs.
>
> Why couldn't PDAs be served by the 'old' driver then? Old doesn't mean obsolete.
>
> Also embedded world != PDAs. I was thinking more of things like PVRs, and blade
> servers. What about solid state video cameras? Are they going to use PIO mode
> ATA?
on common misunderstanding ; PATA != PIO mode ATA but Parallel ATA, as
opposed to Serial ATA
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-25 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 11:19 [RFR] a new SCSI driver john
2003-05-25 10:18 ` Zwane Mwaikambo
2003-05-28 18:25 ` Jörn Engel
2003-05-25 10:45 ` Arjan van de Ven [this message]
2003-05-25 11:48 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2003-05-25 12:09 john
2003-05-25 11:48 john
2003-05-25 10:32 john
2003-05-25 9:44 john
2003-05-25 8:52 ` Zwane Mwaikambo
2003-05-25 9:35 ` Russell King
2003-05-27 0:52 ` Alan Cox
2003-05-25 13:21 ` Jeff Garzik
2003-05-24 19:51 Jeff Garzik
2003-05-26 2:59 ` Douglas Gilbert
2003-05-26 20:52 ` Ishikawa
2003-05-26 15:16 ` Rabeeh Khoury
2003-05-27 11:38 ` Douglas Gilbert
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=1053859525.1571.0.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=jgarzik@pobox.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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