Poulsbo is another example of this. Intel wanted a low-power mobile
graphics chipset and chose to buy in a 3D core from an external vendor. IP
issues prevent them from releasing any significant information about that
3D core, so the driver remains closed source. The implication is pretty
clear - whichever section of Intel was responsible for the design of
Poulsbo presumably had "Linux support" as a necessary feature, but didn't
think "Open driver" was a required part of that.
-- Matthew Garrett
(the entire post is worth reading)
We are removing more crap than we are adding, looks like progress to me! :)
-- Greg Kroah-Hartman
gives an update on the -staging tree
When it [comes] to code coverage, x86 matters _so_ much more than any other
architecture, that verification features like lockdep etc are way more
important on x86 than on anything else.
Sure, there may be locking issues in some arch-specific code, and other
architectures could be better off caring. But the advantage of lockdep for
some pissant architecture that has a very limited user base (maybe lots of
chips, but much more limited _use_ - fewer drivers, fewer workloads etc)
is much lower, since those architectures know that x86 will give them 99%
of the coverage.
-- Linus Torvalds
to post comments)