[8016] in linux-scsi channel archive
Re: Devices not supporting read-6....
daemon@ATHENA.MIT.EDU (Jens Axboe)
Sun Feb 6 15:20:40 2000
Date: Sun, 6 Feb 2000 21:14:35 +0100
From: Jens Axboe <axboe@suse.de>
To: Eric Youngdale <eric@andante.org>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
Drew Eckhardt <drew@Poohsticks.Org>,
"Kenneth D. Merry" <ken@kdm.org>,
Jonas Nickel <jonas.nickel@tu-berlin.de>,
linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu,
phoenix@thesindicate.com
Message-ID: <20000206211435.D692@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <004501bf70da$81f98ca0$0f17a8c0@eric.home>; from eric@andante.org on Sun, Feb 06, 2000 at 02:43:52PM -0500
On Sun, Feb 06 2000, Eric Youngdale wrote:
> Actually I had another thought. There is an even easier way of doing
> things now. When I cleaned up the queueing code, a lot of the similar code
> between sd and sr got moved into scsi_lib.c. Thus teaching sr.c to handle
> writes would be quite trivial. Mainly adjusting sr_init_command() to
> generate a WRITE_10 if the command is a write and the device has the
> writable flag set.
>
> There are a couple of places where it tries to ensure that access is
> read-only (possibly in sr_open) These would need to be modified so that
> they check the writable flag first.
Indeed the changes are trivial, with a DVD-RAM at least. And sr
deos have the write in place in current 2.3 kernels.
I have a DVD-RAM drive handy, I'll try and hack something up.
--
* Jens Axboe <axboe@suse.de>
* Linux CD-ROM Maintainer
* http://www.kernel.dk
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
