Zachary Amsden wrote:
And by NO circumstances, is it required to be a CLOSED source binary
blob. In fact, why can't it be open? In the event of a firmware bug,
in fact, it is very desirable to have this software be open so that
it can be fixed
You're making a very good argument as to why we should probably
require that the code linking against such an interface, if we
decide we want one, should be required to be open source.
I think you will see why our VMI layer is quite similar to a
traditional ROM, and very dissimilar to an evil GPL-circumvention
device.
(?) There are only two reasonable objections I can see to open
sourcing the binary layer.
Since none of the vendors that might use such a paravirtualized
ROM for Linux actually have one of these reasons for keeping their
paravirtualized ROM blob closed source, I say we might as well
require that it be open source.
As for the evilness of a binary interface - the interface between
kernel and userland is a stable binary interface and is decidedly
non-evil. I could see a similar use for a stable paravirtualization
interface, to make compatibility between Linux and various hypervisor
versions easier.
As long as it's open source so the thing can be debugged :)
--
All Rights Reversed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
