On Fri, Aug 12, 2011 at 12:58:10PM +0200, Hans Petter Selasky wrote:
> > Yes, I don't know what is currently going on with this device, sorry.
>
> drivers/usb/serial/pl2303.c
>
> Can someone shed some light into where the following device detection logic is
> derived from?
>
> if (serial->dev->descriptor.bDeviceClass == 0x02)
> type = type_0;
> else if (serial->dev->descriptor.bMaxPacketSize0 == 0x40)
> type = HX;
> else if (serial->dev->descriptor.bDeviceClass == 0x00)
> type = type_1;
> else if (serial->dev->descriptor.bDeviceClass == 0xFF)
> type = type_1;
> dbg("device type: %d", type);
'git blame' is your friend here.
It's been sent to me in different patches over the years from people who
have access to the pl2303 data sheets, which I do not. So I really
don't know, try asking prolific here about this issue, they would know
more.
> I have a PL2303 device which is detected like HX type instead of type_0:
>
> bLength = 0x0012
> bDescriptorType = 0x0001
> bcdUSB = 0x0110
> bDeviceClass = 0x0000
> bDeviceSubClass = 0x0000
> bDeviceProtocol = 0x0000
> bMaxPacketSize0 = 0x0040
> idVendor = 0x067b
> idProduct = 0x2303
> bcdDevice = 0x0300
> iManufacturer = 0x0001 <retrieving string failed>
> iProduct = 0x0002 <USB 2.0 To COM Device>
> iSerialNumber = 0x0000 <no string>
> bNumConfigurations = 0x0001
What happens when you try to use this? Why do you think this isn't a HX
device? Is it because the Device Class is also set to 0x0000? What
type is it really?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
