On 5/12/07, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote:
Add a new ioctl command into driver's ioctl handler, then add a user space program to parse the raw ucode, and send the parsed results to driver through the newly added ioctl command. Driver can then load the results (e.g. text and data segments) into device. Take a look at iwi(4) and iwicontrol(8) for example.
is it really necessary to do it this way? cause i don't like the idea of using a user space program for directing the driver to load the firmware. instead the firmware can be loaded and cached during the device attach routine. the firmware_image_load_file can be the appropriate candidate for such functionality provided that it just returns the raw data from the /etc/xxx firmware file without allocating the dma resources. Cheers kmb -- Something is wrong up on cloud # 9!
