Re: Devices not supporting read-6....

From: Jens Axboe (axboe@suse.de)
Date: Fri Jan 21 2000 - 09:20:17 EST


On Fri, Jan 21 2000, Rogier Wolff wrote:
> 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.

The W1111 doesn't either. And if you look at write-6 we have the
same problem.

>
> 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 updated sd in 2.3 to use READ_10/WRITE_10 whenever possible and
fall back to the 6 byte variants if the device does not support it.
The actual patch is very simple, we just change the ten flag
to read "use only 10 byte read/writes". I've attached it. I
generally don't like the black lists, I'd much rather do it
dynamically.

> 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.

Yes, it gets quite ugly. I battled with the W1111 for some time
before I discovered its READ_6/WRITE_6 weirdness.

> 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...

Still easy ;)

-- 
*  Jens Axboe <axboe@suse.de>
*  Linux CD-ROM Maintainer
*  http://www.kernel.dk


- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:25 EST