On Tue, Aug 03, 2004 at 02:17:22AM -0400, Spiros Papadimitriou wrote:
> Yes, oops, my mistake!
> 
> It is probably Lexar's fault and this is probably a hideous workaround,
> but appending these to unusual_devs.h seems to do the "trick":
> 
> UNUSUAL_DEV(  0x05dc, 0xb013, 0x0000, 0x9999,
>                 "Lexar Media",
>                 "JumpDrive Trio",
>                 US_SC_DEVICE, US_PR_DEVICE, NULL,
>                 US_FL_FIX_INQUIRY),
> 
> UNUSUAL_DEV(  0x05dc, 0xa300, 0x0000, 0x9999,
>                 "LEXAR MEDIA",
>                 "JUMPDRIVE2",
>                 US_SC_DEVICE, US_PR_DEVICE, NULL,
>                 US_FL_FIX_INQUIRY),
> 
> I'm not sure if there are many devices with "broken" (meaning: not
> matching the usb vendor and product strings) INQUIRY responses?  Getting
> them to work and automatically appear on the desktop with updfstab would
> be nice.

It's not 'broken'.... it's just not very descriptive.

I'm not going to merge entries like this, just to get the /proc/scsi/scsi
output (which I'm told is going away eventually) to be 'prettier'.

> The problem is that, rom a short discussion on kudzu bugzilla, updfstab
> *has* to use the info in /proc/scsi/scsi, since the info in
> /proc/bus/usb/devices has no information about the block device that the
> USB storage unit is "mapped" to.

That's why all the information about mapping is now is sysfs.

> Adding UNUSUAL_DEV entries for every such device seems stupid (I'm
> guessing that Windows does not use SCSI INQUIRIES, so vendors do not care
> about that?) and, of course, a pain in the behind.

It uses them, but it just doesn't display the data anywhere prominent.

> Would it make sense at all to str(n)cmp the USB vendor and product strings
> with the appropriate parts of the device's own INQUIRY response and
> "patch" the inquiry response if they do not match?  This should
> "automatically" take care of situations like this, but I have absolutely
> no idea if it breaks other things...

This doesn't make sense -- consider a 'generic' bridge chip attached to a
real spinning-platter media.  You want the INQUIRY of the media (which is
what you get), not of the bridge.

Matt

-- 
Matthew Dharm                              Home: [EMAIL PROTECTED] 
Maintainer, Linux USB Mass Storage Driver

Why am I talking to a toilet brush?
                                        -- CEO
User Friendly, 4/30/1998

Attachment: pgpSD0PU5RHZz.pgp
Description: PGP signature

Reply via email to