> Ken Hahn wrote: <snip> > I just looked at the usb code and it's changed a little while I was gone. > So, I have a few questions. Some of this was in flux when I was around > before. I was just cleaning up before I got this message, and found a print of your original code. I never managed to make it work with my EZUSB chip (and I couldn't find the real drives). Are you using an FX family device?
> Here's a little background first. Our devices are mass storage devices, > however they use the EZ-USB chips that are minus firmware when they are > first turned on. > The device itself actually has a usb connection on one end and a parallel > port on the other. When the device is first plugged in to the USB connector, > a scanning firmware is uploaded to the device. When the device is plugged > into a BACKPACK drive, it renumerates and then uses a new PID to ask for a > firmware that is appropriate for the newly connected device (there are 4 > firmwares in all). Once this firmware is loaded, the device re-numerates > again, and comes up as a standard mass-storage device, to be handled by > usb-storage. It might be better to not put it in the kernel at all, or offer a choice. The linux-hotplug project has great USB support, especially for EZUSB FX/FX2 chips. See http://linux-hotplug.sourceforge.net/?selected=usb - especially the last para. I thought that there were some examples in there already, but I don't see them. The user space tools can be much more easily upgraded, and you don't even need to modify the intel hex file formats - it maps the device ids to a hex file, which then gets downloaded. No effort.... Brad _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
