On Thu, 7 Feb 2008, Fabio Venturi wrote:
> > No, no! Please use the patch in the form I sent to you. The
> > USB_DEVICE macro should say:
> >
> > USB_DEVICE(0x10d6, 0x2200)
>
> Right, network byte order
Not really. You could just as well have written them as 4310 and 8704,
(except that people would think you were weird for using decimal
instead of hex). That is, these are just numbers -- they don't have a
fixed representation in storage.
> My bad :(
> But for some reason the patch is rejected, so I had to type it down by hand.
> Now the device doesn't reboot in a infinite loop, it seems to settle
> after initialization.
The patch is working!
> debugfs is mounted and usbmon is loaded
>
> With the correct VendorID and ProductID something happened
> and dmesg now tells:
...
> and usbmon:
...
That's what they're supposed to say.
> Redirecting stderr and stdout of 'lsusb -v' I get the following details.
> Note: the device restart if it get probed with 'lsusb -v'
>
>
> Bus 001 Device 011: ID 10d6:2200 Actions Semiconductor Co., Ltd
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x10d6 Actions Semiconductor Co., Ltd
> idProduct 0x2200
Notice how this is different from what appears when you left the device
plugged in at boot time, earlier?
...
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP can't get device qualifier: No
> such device
> can't get debug descriptor: No such device
> cannot read device status, No such device (19)
> 3 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 200
>
> // ---------- END OF LSUSB -V --------------
>
> I guess something went wrong.
Probably lsusb triggers that same firmware bug.
> I put a rule in the udev rules directory:
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="10d6",
> ATTRS{idProduct}=="2200", KERNEL=="sd*",
> GROUP="disk", MODE="0664", SYMLINK+="mp3_noblex"
>
> the symink point to usbdev1.12_ep83 that is a
> character special and can't be mounted
I don't understand what wrong, but it's a udev problem rather than a
kernel problem.
Now that the device gets initialized correctly, does it actually work
as it should?
> Just for talking, this is the device:
> http://www.img.starsellersworld.com/500/G_100310788.jpg
>
> Thank you again for your huge help!
You're welcome.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
