From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCHES] add ata scsi driver
Date: 27 May 2003 01:22:56 +0100 [thread overview]
Message-ID: <1053994974.17129.32.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305252236400.10183-100000@home.transmeta.com>
On Llu, 2003-05-26 at 06:40, Linus Torvalds wrote:
> > And for specifically Intel SATA, drivers/ide flat out doesn't work (even
> > though it claims to).
>
> Well, I don't think it claimed to, until today. Still doesn't work?
Even if it did it would at best be a toy. The core IDE layer doesn't
handle SCSI errors properly (needed for ATAPI) except using ide-scsi. It
doesn't handle hot plugging of devices, it doesn't handle tagged
queueing very well, it hasn't the slightest idea about multipath (SATA2
can do), it doesn't know a lot of other things either.
SATA and especially SATA2 is basically SCSI with some slightly odd ways
of issuing READ10/WRITE10 to disk devices. A "native" driver would
basically be a copy of most of drivers/scsi.
I actually think thats a positive thing. It means 2.5 drivers/scsi is
now very close to being the "native queueing driver" with some
additional default plugins for doing scsi scanning, scsi error recovery
and a few other scsi bits.
next prev parent reply other threads:[~2003-05-27 1:13 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 4:58 [BK PATCHES] add ata scsi driver Jeff Garzik
2003-05-26 5:15 ` Linus Torvalds
2003-05-26 5:30 ` Jeff Garzik
2003-05-26 5:36 ` Jeff Garzik
2003-05-26 5:42 ` Linus Torvalds
2003-05-26 6:01 ` Jeff Garzik
2003-05-26 16:56 ` Linus Torvalds
2003-05-26 17:47 ` Jeff Garzik
2003-05-26 20:09 ` Linus Torvalds
2003-05-27 0:29 ` Alan Cox
2003-05-27 6:07 ` Jeff Garzik
2003-05-27 6:30 ` Linus Torvalds
2003-05-27 6:51 ` Linus Torvalds
2003-05-27 7:29 ` Jeff Garzik
2003-05-26 5:40 ` Linus Torvalds
2003-05-26 5:53 ` Jeff Garzik
2003-05-26 6:21 ` Jeff Garzik
2003-05-26 16:57 ` Linus Torvalds
2003-05-26 17:24 ` Jens Axboe
2003-05-26 17:54 ` Jeff Garzik
2003-05-26 17:59 ` Jeff Garzik
2003-05-26 18:11 ` Jens Axboe
2003-05-27 0:22 ` Alan Cox [this message]
2003-05-27 4:15 ` Linus Torvalds
2003-05-26 10:32 ` Bartlomiej Zolnierkiewicz
2003-05-26 11:13 ` Jeff Garzik
2003-05-26 11:37 ` Bartlomiej Zolnierkiewicz
2003-05-26 5:59 ` Benjamin Herrenschmidt
2003-05-26 6:03 ` Jeff Garzik
2003-06-02 9:46 ` Andre Hedrick
2003-06-02 13:56 ` Alan Cox
2003-05-26 18:12 James Bottomley
2003-05-26 18:18 ` Jens Axboe
2003-05-26 18:47 ` James Bottomley
2003-05-26 19:07 ` Jens Axboe
2003-05-26 19:17 ` James Bottomley
2003-05-26 19:33 ` Jens Axboe
2003-05-27 12:39 ` Jens Axboe
2003-05-27 14:26 ` James Bottomley
2003-05-27 17:16 ` Jens Axboe
2003-05-27 18:09 ` James Bottomley
2003-05-27 18:21 ` Jens Axboe
2003-05-27 18:30 ` James Bottomley
2003-05-26 20:27 ` Linus Torvalds
2003-05-26 20:36 ` James Bottomley
2003-05-26 20:45 ` Linus Torvalds
2003-05-26 20:51 ` Jens Axboe
2003-05-26 20:56 ` James Bottomley
2003-05-26 20:38 ` Jens Axboe
2003-05-26 20:49 ` Linus Torvalds
2003-05-26 20:57 ` Jens Axboe
2003-05-26 21:34 ` Linus Torvalds
2003-05-26 23:58 ` Nick Piggin
2003-05-27 0:09 ` Linus Torvalds
2003-05-27 0:49 ` Nick Piggin
2003-05-27 0:16 ` Alan Cox
2003-05-27 6:54 ` Jens Axboe
2003-05-27 14:20 ` James Bottomley
2003-05-27 14:36 ` Linus Torvalds
2003-05-27 14:59 ` James Bottomley
2003-05-27 15:21 ` Jeff Garzik
2003-05-27 15:38 ` James Bottomley
2003-05-27 15:50 ` Jeff Garzik
2003-05-27 16:00 ` James Bottomley
2003-05-27 16:16 ` Jeff Garzik
2003-05-28 9:35 ` Christoph Hellwig
2003-05-28 10:50 ` Lincoln Dale
2003-05-27 19:43 ` Jens Axboe
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=1053994974.17129.32.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).