Salyzyn, Mark wrote:
For instance, there are reasons, somewhat outside the control of the
Hardware Vendor, for binary drivers. Often, in the hopes of achieving
standards compliance, Hardware vendors are cornered by legalities over
the copyright associated with those standards that ties their hands
either from releasing interface documentation or from releasing source
code. Yet all these vendors would be overjoyed to have Linux drivers for
their Hardware in order to increase the sales of their products.
Uh, a copyrighted standard? They are trying to live up to a secret
standard, one they cannot publish?
Don't sound like a standard to me - a standard is something known,
that is the purpose of standardization.
This sounds like "we standardized the voltage for household lamps, but
we won't tell if it is 110V, 220V or something completely different."
I really hope I misunderstood this.
Standards compliance should never get in the way of open source.
Sure - if the owner modifies the source, then the thing may no longer
comply with the standard. In some cases even illegal or dangerous.
But in that case, it is the fault of the owner, not the vendor. The vendor
can simply say that anyone changing the (distributed) source should get
their own certification.
Helge Hafting
-
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]