Arjan, by definition the firmware has to be tied to the kernel somehow.
THe datastructure and other aspects are often tied directly to
the firmware version loaded.

At first, people said "hey we're going to make the firmware loadable
from userspace, so sorry now you can't load your driver without a
ramdisk, sorry!"  And that royally pissed me off, and directly impacted
my work flow negatively.

Now, for the cases where we do have in-kernel firmware still, people
are suggesting to seperate that out to a seperate tree as well.
Sorry, that's taking things too far.  I've fought, like, forever, to
keep the tg3 driver with it's firmware in-tree.  I refuse to let the
driver get broken like that, it's staying working, and that means
in-tree and linked into the driver.

If debian or whoever else have these concernes and want to rip the
firmware out, it is one hundred percent their problem to patch things
out of the kernel tree they use.

At least from my perspective this looks like a transfer of burdon from
the folks who want to rip the firmware out, to those of us who find
high value in the firmware staying in the tree.

This is really irritating me, because this is one huge case of frickin
Animal Farm.  First a little was taken away, then a little bit more,
and by the end you have something absolutely nobody would have agreed
to from the beginning.
--
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/