[8032] in linux-scsi channel archive
Re: Devices not supporting read-6....
daemon@ATHENA.MIT.EDU (Rogier Wolff)
Mon Feb 7 08:47:29 2000
Message-Id: <200002071341.OAA01259@cave.bitwizard.nl>
In-Reply-To: <004501bf70da$81f98ca0$0f17a8c0@eric.home> from Eric Youngdale at
"Feb 6, 2000 02:43:52 pm"
To: Eric Youngdale <eric@andante.org>
Date: Mon, 7 Feb 2000 14:41:56 +0100 (MET)
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
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Eric Youngdale wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> 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.
See, you can see that I don't keep an eye on the SCSI stuff, and that
you guys DO know what you're doing. Keep up the good work. I'll be
happy to work with you to neaten up DVD RAM support, or to "hand over"
the job to someone who knows what he's doing.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
"I didn't say it was your fault. I said I was going to blame it on you."
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
