Re: firmware loading

2007-05-13 Thread Max Laier
icenses that require a user to acknowledge something before they can use the firmware. See for instance http://www.prweb.com/releases/2007/03/prweb509818.htm > (3) There is a kernel firmware loading facility in > sys/kern/kern_firmware.c. Again, the file cannot be loaded at >

Re: firmware loading

2007-05-12 Thread Chris Turner
Matthew Dillon wrote: > kern/kern_firmware.c will take care of the DMA resources. It looks > quite nifty, but I'm not sure how well it actually works since nothing > is using it yet. Johannes and Joerg committed it a long time ago, > back in 2005. > Not knowing the history - can

Re: firmware loading

2007-05-12 Thread km b
it at attach time. (3) There is a kernel firmware loading facility in sys/kern/kern_firmware.c. Again, the file cannot be loaded at attach time but this way you could have an ioctl that just passes the filename to the driver as part of the RC boot sequence and the

Re: firmware loading

2007-05-12 Thread Matthew Dillon
out allocating the dma resources. : :We will always need to allocate DMA resources for the firmware loading. : :Best Regards, :sephe : :-- :Live Free or Die kern/kern_firmware.c will take care of the DMA resources. It looks quite nifty, but I'm not sure how well it actually works since

Re: firmware loading

2007-05-12 Thread Matthew Dillon
at attach time. (3) There is a kernel firmware loading facility in sys/kern/kern_firmware.c. Again, the file cannot be loaded at attach time but this way you could have an ioctl that just passes the filename to the driver as part of the RC boot sequence and the driver cou

Re: firmware loading

2007-05-12 Thread Sepherosa Ziehau
it just returns the raw data from the /etc/xxx firmware file without allocating the dma resources. We will always need to allocate DMA resources for the firmware loading. Best Regards, sephe -- Live Free or Die

Re: firmware loading

2007-05-11 Thread km b
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 se

Re: firmware loading

2007-05-11 Thread Sepherosa Ziehau
On 5/12/07, km b <[EMAIL PROTECTED]> wrote: Hi All, I have started working on the iwi (3945abg) driver. From the linux BTW, you can use any 3~4 letters as the new driver's name, but don't make it conflicting with the existing one :). iwi(4) has been taken (2200 and 2945 parts) Best Regards,

Re: firmware loading

2007-05-11 Thread Sepherosa Ziehau
On 5/12/07, km b <[EMAIL PROTECTED]> wrote: Hi All, I have started working on the iwi (3945abg) driver. From the linux refrence driver, I have derived the format of the ucode and how to load the ucode onto the card. However, I am not sure how to load the raw ucode, before I can parse the ucode a

firmware loading

2007-05-11 Thread km b
Hi All, I have started working on the iwi (3945abg) driver. From the linux refrence driver, I have derived the format of the ucode and how to load the ucode onto the card. However, I am not sure how to load the raw ucode, before I can parse the ucode and load it onto the firmware. Do I have to re