From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: CD writing - related question
Date: Mon, 30 Jan 2006 18:30:29 -0500 [thread overview]
Message-ID: <43DEA195.1080609@tmr.com> (raw)
Please take this as a question to elicit information, not an invitation
for argument.
In Linux currently:
SCSI - liiks like SCSI
USB - looks like SCSI
Firewaire - looks like SCSI
SATA - looks like SCSI
Compact flash and similar - looks like SCSI
ATAPI - looks different unless ide-scsi used
Was there a reason, a technical reason, why the minor blotches in
ide-scsi weren't fixed so that everything could look the same and share
the same device naming form? The DMA issue is solved for blocks, and
several people have stated to the list that the remaining issues could
be solved in minimal time. Seeing no disagreement, I'll assume that's true.
There are separate IDE drivers for disk, tape, floppy, and CD, and the
only reason I ever heard was that ide-scsi adds overhead. I did some
tests using a mighty Pentium-II 350, and there was no overhead with disk
or CD (within the limits of measurement). So there's no huge CPU
penalty, why then the decision to have the separate ide drivers?
The last time I tried, there was one thing which didn't work quite right
doing ZIP drives unless ide-scsi was used, and MO drives don't seem to
work any other way, but I haven't tried since about 2.6.6 or so, that
info could be dated.
This is NOT an argument for change, it may be a reminder that ide-scsi
is not unused, I just never saw any technical reason mentioned.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next reply other threads:[~2006-01-30 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 23:30 Bill Davidsen [this message]
2006-02-01 21:04 ` CD writing - related question Pavel Machek
2006-02-02 16:49 ` Jan Engelhardt
2006-02-02 19:40 ` Bill Davidsen
2006-02-02 20:19 ` Pavel Machek
2006-02-03 2:36 ` Bill Davidsen
2006-02-02 20:39 ` Jens Axboe
2006-02-02 21:05 ` Krzysztof Halasa
2006-02-02 20:35 ` Jens Axboe
2006-02-07 9:22 ` Matt Keenan
2006-02-07 11:04 ` Xavier Bestel
2006-02-07 13:47 ` Bill Davidsen
2006-02-07 13:40 ` 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=43DEA195.1080609@tmr.com \
--to=davidsen@tmr.com \
--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