> This chip, DIB3000P, is supported by the dvb driver, however this particular > implimentation is different. Normally, the device appears on the usb bus as > a particular VID/PID, the firmware is downloaded, the device disconnects > itself from the bus and reconnects with the PID incremented by one, eg from > 0xd000 at first plugin to 0xd001 after download and initialization.
I've written this so many times, that I'm starting to leave things out. Here's the missing but crucial bit which seems to be the root of most problems.
This device is different because after firmware download it disconnects and reappears on the USB bus as the same PID. All the sniffers I've tried apparently decide that this was an aborted plugin, or just have a bug, and throw away the captured firmware.
Thanks, glen.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
