From: Jeff Garzik <jgarzik@pobox.com>
To: john@grabjohn.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFR] a new SCSI driver
Date: Sun, 25 May 2003 09:21:40 -0400 [thread overview]
Message-ID: <3ED0C364.3020507@pobox.com> (raw)
In-Reply-To: <200305250944.h4P9i5Ct000456@81-2-122-30.bradfords.org.uk>
john@grabjohn.com wrote:
>>Serial ATA is looming quickly on the horizon. Both device and host
>>controller SATA implementations really lend themselves to behaviors
>>that have existed in SCSI for a while. SATA even defines use of SCSI
>>Enclosure Services.
>
>
> 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.
>
> This would save having any more than the minimum SATA code going in to the
> existing IDE driver, and consolidate work in the future.
I'm content to let evolution make these decisions... predicting into
the future isn't the best skill a technologist has :)
Jeff
next prev parent reply other threads:[~2003-05-25 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 9:44 [RFR] a new SCSI driver john
2003-05-25 8:52 ` Zwane Mwaikambo
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-25 12:09 john
2003-05-25 11:48 john
2003-05-25 11:19 john
2003-05-25 10:18 ` Zwane Mwaikambo
2003-05-25 10:18 ` Zwane Mwaikambo
2003-05-28 18:25 ` Jörn Engel
2003-05-28 18:25 ` Jörn Engel
2003-05-25 10:45 ` Arjan van de Ven
2003-05-25 11:48 ` Russell King
2003-05-25 10:32 john
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=3ED0C364.3020507@pobox.com \
--to=jgarzik@pobox.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.