On 12-06-13 04:44 PM, Ross Burton wrote:
Hi,
My current test hardware for Yocto work is a Celeron-class Sandy Bridge-based micro PC.
As is to be expected for a machine like this, it's got modern Intel graphics and
wireless. Neither of which are supported by atom-pc, as it's nominally a "generic
netbook" image.
Let's face it -- it's a really bad generic netbook image, it's really a Asus
eeePC701-and-similar image. Specifically, only one wifi driver, only i915 GPU
driver, and so on.
I'm not arguing for a true generic kernel such as Fedora maintains which boots
on almost everything, just a new machine with more flexibility. Including both
i915 and i965 GPU drivers covers everything Intel-driven from the earliest
netbook to the latest Ivy Bridge[1]. Including the iwl wifi drivers at least
covers a good proportion of devices out there. There are probably a few more
drivers that are common and give big gains in support. Not exactly boot on
everything, but certainly boot on many.
Thoughts?
Send patches, and define the machine. But it has to be something
that we can actually *test* and maintain. We don't define 'what if'
and 'in case' configurations. We define embedded/tight configurations
that should be extended for particular machines.
The common-pc is a bit old, so I'd suggest sending patches to that
base and we can consider them on a 1:1 basis. As long as it isn't
overly generic, and hits a defined/closed set of machines and drivers,
patches won't be denied.
Even better, just branch from one of the existing configs and add more,
that way the extensions are separate from the base.
Cheers,
Bruce
Ross
[1] Ignoring Cedar Trail, but that's already in meta-intel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
