On Wed, Dec 19, 2001 at 03:56:22PM -0500, [EMAIL PROTECTED] wrote: > > The actual loading of the DSP code into the driver isn't the issue I'm > trying to resolve right now - I'm hoping by the time I need to resolve > it, you folks will have hammered out the details of this firmware > loading thread (maybe their already hammered out). What I need to > resolve is the internal processing of the data. All the other drivers > allocate a big chunk of memory (1 megabyte), turn the hex data into a > binary format, then free the hex data. However, when I tried that here, > my kmalloc failed. Should I be using vmalloc for this operation?
If you have the data in a .h file, can't you just iterate through the data and send it to a function that allocates a small buffer for the urb, copies the data into there, and then sends the urb? This is how the usb-serial drivers that download firmware to the device work. thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
