> The consequence would be that $COMPANY writes a driver and blames the
> rest of the Linux world to change some internal undocumented interface
> months lateron just that they can commercially state to "support Linux"
> but without any real reason. In the non-evolutionary Windows world this
> holds until the next major release, but not on the high-tech front.
It should be possible to define a reasonable set of requirements that one
must meet in order to claim to "support Linux", just as Microsoft does for
Windows. One requirement should definitely be that driver source code be
available to everyone who purchases the hardware and that all (or at least
sufficient) interfaces to the hardware be well-documented.
DS
-
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]
