>I've the same problem, my device driver ue a carry chips too. In november,
>i've
>ask how to solve this problem. For my driver (HH501, look last week archive),
>you load the firmware and the driver renumerate itsef. Then you can use
>it. For
>using this device, you can boot under windows, reboot, and linux/bsd can use
>this driver. This is A solution, not the best. To load the firmware, i use a
>tool in user space, call by hotplug. So you can extract the firmware from the
>kernel.
If you want to use Firmware that ReEnumerates, don't do this from a
usb-storage device !
Register another usb-driver with it's own MODULE_DEVICE_TABLE and do the
Firmware donload from there.
I've done this with ReEnumerating PSI Firmware - works fine.
>I've made a perl script witch parse the snoopusb log, to extract the firmware.
>Note my original driver (comes with device) doesn't work with my windows. So i
>use google to find update and i have found a new version of the driver. This
>driver have the same release than UISxxx from Carry, but you can't interchange
>file.
Check http://www.carry.com.tw/supports/supports_dl.htm for a driver that
works with your device.
I had the same problem with a device from 'PSI' : the driver I got on the
PSI CD does ReEnumerate, the original carry driver doesn't.
>I've NO documentation at all from Carry, or all other compagnies. I use some
>informations found from sddr09, smil but that's all. I look quickly your
>patch,
>and we use the same format of the command, the same patch to code block
>number,
>but the method differ, it's near the smil library from toshiba.
All the block number codings should be ok, since carry sent us some specs
under NDA.
>This week, i've began to code the write function. It works under some
>conditions.
Write for which devices ? SSFDC or CompactFlash ?
- sda
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
