HEADSUP!!! USB MFC committed..

[Peter Radcliffe]

Julian Elischer <julian at elischer.org> probably said:
> The USB code in RELENG_4 has been updated to match that in -current.
> Please test any USB devices that are critical to you BEFORE we release
> 4.10 :-)

Since you said you were working on USB fixes in general, I've got a
Pentax Optio S4 that comes up as umass0 and never gets a disk device
assigned to it with -stable. My USB CF reader gets assigned da0 as I
expect it to.

  umass0: PENTAX PENTAX OPTIO S4, rev 1.00/10.00, addr 2

  port 1 addr 2: full speed, self powered, config 1,
    PENTAX OPTIO S4(0x0006), PENTAX(0x0a17), rev 10.00

They re-used the same device id from the 330 ?

  usbdevs:vendor ASAHIOPTICAL     0x0a17  Asahi Optical
  usbdevs:/* Asahi Optical products */
  usbdevs:product ASAHIOPTICAL OPTIO330   0x0006  Digital camera

There is one quirk already;

        /*
         * The Pentax Optio cameras require RS_NO_CLEAR_UA
         * PR: kern/46369, kern/50271
         */
        if (UGETW(dd->idVendor) == USB_VENDOR_ASAHIOPTICAL) {
                sc->quirks |= RS_NO_CLEAR_UA;
        }

Some googling turns up references to this camera on linux mailing lists,
but I can't translate the UNUSUAL_DEV to what it needs for FreeBSD;

  <per.winkvist:uk.com>:

      * USB storage: Make Pentax Optio S4 work

  +/* Submitted by Per Winkvist <per.winkvist at uk.com> */
  +UNUSUAL_DEV( 0x0a17, 0x006, 0x1000, 0x9009,
  +                "Pentax",
  +                "Optio S",
  +                US_SC_8070, US_PR_CBI, NULL,
  +                US_FL_FIX_INQUIRY ),

Uh, help please ?

P.

-- 
pir