if only the firmwares could live together in one folder or different folders... then, the bash script can be triggered to install the appropriate FW each time we install a new kernel and clean unused FW if we no longer have a kernel that uses it.
let's not forget that all this is documented in b43 website (http://wireless.kernel.org/en/users/Drivers/b43) so let see how this transit period between legacy and new b43 drivers goes :-) On Mon, Jun 9, 2008 at 6:09 PM, Rene Engelhard <[EMAIL PROTECTED]> wrote: > Hi, > > Nadav Kavalerchik wrote: > > i confirm that the new firmware is not compatible with 2.6.24 kernel > > > > but you could have the bash script install different firmware to > > different kernels ? can you ? > > I could, but what will happen when the kernel gets upgrded from .24 to > .25? b43-fwcutter won't be upgraded. (although, hmm, that probably can > be solved with a trigger now and is not worse than now anyway..)) > > Or you install .25, install b43-fwcutter and for whatever reason revert > to testings .24.... -> boom. > > But I'll think about it... > > Regards, > > Rene >
