Curiousity regarding data pointer for usb_bulk_msg.
Over at the prism54 project http://prism54.org , work has
just started on adapting the driver for the USB devices.
All of these Prism GT chipsets require a firmware to be loaded.
This , of course, is done by the kernel firmware loader routine request_firmware.
Now the curiousity; if we use a pointer to the data area as returned
from request_firmware, it doesn't work. If, however, we use the stack
(or a kmalloc'ed area) and copy over and pass the stack (or km'ed area)
address, then it works.
Only thing I could find is that request_firmware allocates the data area
using vmalloc. Why is this a problem ?


Thanks.

Margit




------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to