Re: ipw2200 [was Re: RFC: Starting a stable kernel series off the 2.6 kernel]

[Pavel Machek <pavel@suse.cz>]

On So 10-12-05 23:30:30, Rob Landley wrote:
> On Saturday 10 December 2005 02:35, Pavel Machek wrote:
> > On Wed 07-12-05 12:14:25, Rob Landley wrote:
> > > On Tuesday 06 December 2005 12:51, Bill Davidsen wrote:
> > > > Just so we're all on the same page, I think there are two sets of
> > > > unhappy people here... one is the group who want new stuff fast and
> > > > stable. For the most part that's not me, although I was in the "if
> > > > you're going to add ipw2200 support, why not something that works?"
> > > > group. But new stuff is going in faster than most people can assimilate
> > > > it if they have a real job, so I don't see too much problem there.
> > >
> > > My laptop has an ipw2200 but I can't get it to work in any kernel I built
> > > because the kernels I build aren't modular.  I hope to be able to work
> > > around this someday with a clever enough initramfs (if necessary, moving
> > > the initramfs initialization earlier in the boot sequence), but it hasn't
> > > made it far enough up my todo list yet.
> >
> > Well, building modular kernel for a test is not *that* much work.
> > Anyway, if you are going to fix it, fix it properly (by
> > delayed firmware loading) -- initrd hacks are good for you
> > but unusable for anyone else.
> 
> I don't see why that's any less usable than using udev from initramfs to find 
> your root partition.

Why use udev from initramfs? Just teach ipw2200 to load firmware
late. Don't load firmware when ipw2200 is initialized, load it only
when someone attempts to talk to your ipw2200. At that time, you
should have userland already.
								Pavel
-- 
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/