>Number:         23920
>Category:       kern
>Synopsis:       usb umass driver quirk
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 29 01:10:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6.2_RC3
>Organization:
R. Braun
>Environment:
System: NetBSD skywalker.sceen 1.6.2_RC3 NetBSD 1.6.2_RC3 (SKYWALKER) #0: Sun Dec 21 11:26:55 CET 2003 syn@skywalker.sceen:/usr/src/sys/arch/i386/compile/SKYWALKER i386
Architecture: i386
Machine: i386
>Description:
A quirk is usually needed for MSYSTEMS DiskOnKey usb keys. It sometimes work
without it but it usually doesn't. The device is detected, but it's not attached
as a block device (i'm using an scsi layer).
>How-To-Repeat:
Plug a MSYSTEMS DiskOnKey usb key to a usb hub and see dmesg output.
>Fix:
The UMASS_QUIRK_NO_MAX_LUN quirk does the job. Here is a patch for
dev/usb/umass_quirks.c :

--- umass_quirks.c.old  Mon Dec 29 02:07:30 2003
+++ umass_quirks.c      Mon Dec 29 02:08:06 2003
@@ -100,7 +100,7 @@
 
        { { USB_VENDOR_MSYSTEMS, USB_PRODUCT_MSYSTEMS_DISKONKEY },
          UMASS_WPROTO_UNSPEC, UMASS_CPROTO_UNSPEC,
-         UMASS_QUIRK_NO_MAX_LUN,
+         0,
          PQUIRK_NOMODESENSE | PQUIRK_NODOORLOCK | PQUIRK_NOBIGMODESENSE,
          UMATCH_DEVCLASS_DEVSUBCLASS_DEVPROTO,
          NULL, NULL

Hope it helps ;-).
>Release-Note:
>Audit-Trail:
>Unformatted: