Re: ipw2200 only works as a module?

[Alistair John Strachan]

On Wednesday 19 October 2005 22:35, Rob Landley wrote:
> On Monday 26 September 2005 12:12, Luca wrote:
> > Keenan Pepper <keenanpepper@xxxxxxxxx> ha scritto:
> > > With CONFIG_IPW2200=y I get:
> > >
> > > ipw2200: ipw-2.2-boot.fw load failed: Reason -2
> > > ipw2200: Unable to load firmware: 0xFFFFFFFE
> > >
> > > but with CONFIG_IPW2200=m it works fine. If it doesn't work when built
> > > into the kernel, why even give people the option?
> > >
> > > BTW, a better error message than "Reason -2" would be nice. =)
> >
> > -2 is -ENOENT (no such file or directory). ipw2000 requests its firmware
> > using a hotplug event, but when the driver is compiled into the kernel
> > it gets loaded _before_ the root fs is mounted and of course the hotplug
> > system and the firmware are not available.
>
> Any possibility of extracting initramfs early enough that the firmware
> could live in there when this sucker's built in?
>

Another possible solution would be to delay initialisation of the hardware 
until the network interface is brought up. This is a more robust approach 
because then if something bad happens and the firmware needs to be reloaded, 
you can just cycle the interface (ifdown/ifup) and the firmware will be 
reuploaded.

An example of hardware doing this is the prism54 driver (also in tree) which 
delays loading the firmware until it absolutely has to. This driver survives 
being built-in quite happily.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/