From: Pascal Schmidt <der.eremit@email.de>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Making MO drive work with ide-cd
Date: Sun, 18 Jan 2004 02:16:18 +0100 [thread overview]
Message-ID: <E1Ai1Y2-0000cj-00@neptune.local> (raw)
In-Reply-To: <1f8mw-3Qk-1@gated-at.bofh.it>
On Sun, 18 Jan 2004 00:50:04 +0100, you wrote in linux.kernel:
> By some coincidence I got hold of an MO drive today. Under 2.4.21
> and 2.6.1 using ide-scsi all seems to work at first sight.
For me, it doesn't work at all with ide-scsi in 2.6. 2.4 is fine
in that regard.
> With ide-cd I get errors only.
> Not surprising: ide-cd expects a CD so sends READ_TOC and
> gets "illegal request / invalid command" back.
> The appropriate command is READ CAPACITY.
There is a patch by me with some rework by Jens Axboe in -mm that
corrects this situation. It hasn't seen much testing, though.
By the way, what hardware sector size does your MO use? I have
only tested my patch with 2048 byte sector size - everything else
is unlikely to work with ide-cd...
> Are there cases where ide-cd is useful?
> Should we retarget ide_optical to ide-scsi?
Please fill the whole disk and then reread and compare via ide-scsi.
That never worked for me in 2.6 using ide-scsi, but it does work
with the patch in -mm.
I agree that the situation in mainline as it is now is undesirable,
only mounting prewritten discs read-only works.
--
Ciao,
Pascal
next parent reply other threads:[~2004-01-18 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f8mw-3Qk-1@gated-at.bofh.it>
2004-01-18 1:16 ` Pascal Schmidt [this message]
2004-01-18 21:28 Andries.Brouwer
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 17:18 Andries.Brouwer
2004-01-18 17:58 ` Kevin P. Fleming
2004-01-18 18:34 ` Bartlomiej Zolnierkiewicz
2004-01-18 22:30 ` Pascal Schmidt
2004-01-18 12:20 Andries.Brouwer
2004-01-18 12:36 ` Pascal Schmidt
2004-01-18 20:48 ` Willem Riede
2004-01-17 23:38 Andries.Brouwer
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=E1Ai1Y2-0000cj-00@neptune.local \
--to=der.eremit@email.de \
--cc=Andries.Brouwer@cwi.nl \
--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
all inboxes | Powered by JetHome®