[7870] in linux-scsi channel archive
Devices not supporting read-6....
daemon@ATHENA.MIT.EDU (Rogier Wolff)
Fri Jan 21 11:00:39 2000
Message-Id: <200001202306.AAA22947@cave.bitwizard.nl>
To: linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
Date: Fri, 21 Jan 2000 00:06:42 +0100 (MET)
Cc: 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
Hi,
As far as I know, "read-6" is a very mandatory command. However
there is a device, the
{"TOSHIBA","DVD-RAM SD-W1101","*", BLIST_GHOST},
which doesn't implement it.
What do we do?
- Blacklist it as "doesn't support read-6" and implement
stuff to prevent read-6 if that flag is set?
- Ignore the issue, and just let people with this hardware
live with a non-working drive?
Is there maybe already something implemented? Anybody the "owner" of
that piece of code?
I seem to own the "blist_ghost" stuff, so it's going to be listed
there, but then the system runs into not-working read-6 commands.
Roger.
P.S. (I'm not on linux-scsi, and I'm on vacation starting saturday).
I had been hoping it would've been as easy as listing the drive as
a 'blist_ghost' thing, but now things are more complicated...
--
** 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
