Subject: Re: iwictl program location and the iwi driver (for Intel 2200BG)
To: None <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 01/12/2005 14:09:41
In article <firstname.lastname@example.org>,
Love <email@example.com> wrote:
>firstname.lastname@example.org (Christos Zoulas) writes:
>> In article <email@example.com>,
>> Sverre Froyen <firstname.lastname@example.org> wrote:
>>>Now that Damien Bergamini's iwi driver is in the tree, it seems
>>>pertinent to consider the location of the iwictl program and the
>>>associated Intel firmware. Obviously, the firmware needs to be loaded
>>>PS This likely applies to the ipw driver as well.
>> I would prefer that we don't grow 1 ctl program per driver and come
>> up with a generalized firmware loader infrastructure.
>Framework that the kernel could load the drivers firmware, userland
>program, or bootloader load a new module (just like kernel modules in
>FreeBSD), or all of the three ?
All three, in the order you mentioned them :-)
1. Have a framework that device drivers can use to load firmware.
2. Have a userland program that all drivers can use to load firmware.
a. Make everything a module.
b. Associate drivers with firmware files to be loaded upon probe.