> Were's the initrd going to get the firmware? It's not in the freakin' tree
> anymore. If I have to go download a firmware image and stick it in an
> initrd, why the hell wouldn't I just plug it directly into the kernel?
> It's *my* kernel.
Well initrd is _user_ space so it probably gets them from user space tools.
> Oh for the love of God, will you people stop drooling over the fucking GPL?
> It's *firmware*... it's just a bunch of bits. It's *not* a program the
> kernel executes. It's just data. (__init_data to be exact.)
Look, if its not distributable then its no good to anyone.
> a lot of company. Ask yourself, will you miss 128_K_ in a machine with a
> fiber channel card in it? It "bloats" the kernel for people using that
> hardware -- machines that don't need it can release it.
Well maybe, and whats the right way to do that, oh my god I do believe its
an initrd.
Well well well
Alan
-
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/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:46 EST