On 06/13/2012 03:50 PM, Stewart, David C wrote:
>> From: [email protected] [mailto:yocto-
>> [email protected]] On Behalf Of Ross Burton
>> Sent: Wednesday, June 13, 2012 1:45 PM
>>
>> 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 thought we had some Sandy Bridge BSP already?

We do. The problem is that doesn't define things like which wifi device
is used. There seems to be a reasonable amount of interest in a much
more generally useful x86 BSP. This seems to fit the goals of the
atom-pc BSP, which has become a bit stale.

> 
>> 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?
>>
>> 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
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to