On Sun, 26 Oct 2003, Jon Wilson wrote:
> Alan Stern wrote:
> >
> >That last message is very odd. It indicates something might be wrong with
> >your camera. Can you post the output from "lsusb -v" with your camera
> >plugged in and turned on?
> >
> >
> Attached. This is with a 2.4.22 kernel, with which the cam works fine.
> I can boot into a 2.6.0-test8 kernel and redo this if needed.
>
> Jon
Bus 001 Device 002: ID 0919:0100 Tiger Electronics Fast Flicks Digital Camera
Language IDs: none (invalid length string descriptor bf; len=0)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0919 Tiger Electronics
idProduct 0x0100 Fast Flicks Digital Camera
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 129
bNumInterfaces 1
bConfigurationValue 0
iConfiguration 0
bmAttributes 0x80
MaxPower 190mA
I won't bother with the rest. That bConfigurationValue = 0 is illegal;
your camera is not compliant with the USB 2.0 spec.
However, that doesn't explain what the problem is. 2.6.0-test8 should
work okay even with that illegal value there. Maybe it's indicative of
some other incompatibility that 2.6 is more strict about?
Alan Stern
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
