All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: yocto@yoctoproject.org
Subject: More useful generic-x86 machine
Date: Wed, 13 Jun 2012 21:44:50 +0100	[thread overview]
Message-ID: <21DFE0D0610B43B982449CB678019727@intel.com> (raw)

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?

Ross

[1] Ignoring Cedar Trail, but that's already in meta-intel


             reply	other threads:[~2012-06-13 20:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 20:44 Ross Burton [this message]
2012-06-13 20:47 ` More useful generic-x86 machine Darren Hart
2012-06-13 20:52   ` Ross Burton
2012-06-13 20:55     ` Bruce Ashfield
2012-06-13 21:00       ` Darren Hart
2012-06-13 21:09         ` Bruce Ashfield
2012-06-13 20:49 ` Bruce Ashfield
2012-06-13 22:50 ` Stewart, David C
2012-06-14  0:39   ` Darren Hart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21DFE0D0610B43B982449CB678019727@intel.com \
    --to=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.