"Dunlap, Randy" wrote:
>
> Hi,
>
> Got it figured out yet?
> Here are some clues and/or opinions if you want/need them.
If you are fixing Randy's stuff, you might like to fix
up the rest of the descriptors. See below.
If you are just trying to make a driver, maybe you can
fudge the descriptors within the driver. They are cached,
so it might work out OK...
Brad
>
> > -----Original Message-----
> > From: Alastair Foster [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, March 06, 2001 7:50 AM
> > To: Dunlap, Randy; [EMAIL PROTECTED]
> > Subject: RE: [Linux-usb-users] Two Quick Questions
> >
> > On Mon, 5 Mar 2001, Dunlap, Randy wrote:
> > > Date: Mon, 5 Mar 2001 17:43:58 -0800
> > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
> > > [EMAIL PROTECTED]
> > > From: "Dunlap, Randy" <[EMAIL PROTECTED]>
> > > Subject: RE: [Linux-usb-users] Two Quick Questions
[snip]
> > "Mar 3 19:12:53 localhost kernel: usb.c: USB new device
> > connect, assigned device number 2
> > Mar 3 19:12:53 localhost kernel: usb.c: USB device 2 (prod/vend
> > 0x6bd/0x403) is not claimed by any active driver.
> > Mar 3 19:12:53 localhost kernel: Length = 18
> > Mar 3 19:12:53 localhost kernel: DescriptorType = 01
> > Mar 3 19:12:53 localhost kernel: USB version = 1.00
Maybe should be 1.1?
> > Mar 3 19:12:53 localhost kernel: Vendor:Product = 06bd:0403
An Agfa-Gevaert NV ePhoto CL18 Camera?
> > Mar 3 19:12:53 localhost kernel: MaxPacketSize0 = 8
> > Mar 3 19:12:53 localhost kernel: NumConfigurations = 1
> > Mar 3 19:12:53 localhost kernel: Device version = 1.00
> > Mar 3 19:12:53 localhost kernel: Device Class:SubClass:Protocol =
> > 00:00:00
[snip]
This is OK (per-interface classes)
> > Mar 3 19:12:53 localhost kernel: bInterface
> > Class:SubClass:Protocol = 00:00:00
[snip]
> > Mar 3 19:12:53 localhost kernel: bInterface
> > Class:SubClass:Protocol = 00:00:00
[snip]
> > Mar 3 19:12:53 localhost kernel: bInterface
> > Class:SubClass:Protocol = 00:00:00
[snip]
> > Mar 3 19:12:53 localhost kernel: bInterface
> > Class:SubClass:Protocol = 00:00:00
But these aren't. USB spec 1.1, Table 9-9 states that
"A value of zero is reserved for future standardization".
USB 2.0 Table 9-12 says the same.
You either want a class code, or a Class code of FF.
Probably FF:FF:FF is the Right Thing.
Brad
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-users
