On Mon, 14 Jul 2008, David Miller wrote:
quoted text
> 
> Jeff's not against request_firmware() in an of itself.
> 
> He's against the fact that it's not possible to build a
> self-contained foo.ko module file any longer, and that
> would definitely be possible with using request_firmware().

.. but is it really that big of a deal?

If it were about not being able to build a self-contained non-modular 
"vmlinux", I'd be upset too.

But once you can load a module, you can load the firmware. You just have 
to _remember_ to move it along with the module.

I mean really, you're the one who was complaining that there was no 
technical reason, but now you're apparently using the "alzheimer's 
defense". 

Besides, it's not even true that foo.ko modules are self-contained. We've 
for years and years (pretty much since day one) had nesting module models, 
where in order to load foo.ko you need to load baz.ko first. Yes, the 
firmware file is named differently, but it _is_ different.

			Linus
--
unsubscribe notice
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/