All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>,
	Bruce Ashfield <bruce.ashfield@windriver.com>,
	Saul Wold <sgw@linux.intel.com>
Subject: [PATCH 0/1] [linux-yocto-3.2][meta] common-pc: Add PCNET32 to the config
Date: Fri, 23 Mar 2012 14:52:50 -0700	[thread overview]
Message-ID: <cover.1332539317.git.dvhart@linux.intel.com> (raw)

In support of the self-hosted-image, add CONFIG_PCNET32 to the common-pc BSP
default cfg. This enables the qemux86 image to be run on both qemux86 machines
as well as the vmware 32b machine. Since the qemux86 machine optionally supports
pcnet, this seems a reasonable compromise to managing a dedicated BSP for a
self-hosted-image machine which would be superset of the qemux86 machine.

As this is a single CONFIG_ option, add it to the common-pc.cfg directly, rather
than defining a new feature.

The following changes since commit 514847185c78c07f52e02750fbe0a03ca3a31d8f:

  meta: update kver to v3.2.11 (2012-03-16 10:42:41 -0400)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib dvhart/meta/pcnet
  http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/meta/pcnet

Darren Hart (1):
  [meta] common-pc: Add PCNET32 to the config

 meta/cfg/kernel-cache/bsp/common-pc/common-pc.cfg |    3 +++
 meta/cfg/kernel-cache/bsp/common-pc/hardware.cfg  |    1 +
 2 files changed, 4 insertions(+), 0 deletions(-)

-- 
1.7.5.4



             reply	other threads:[~2012-03-23 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 21:52 Darren Hart [this message]
2012-03-23 21:52 ` [PATCH 1/1] [meta] common-pc: Add PCNET32 to the config Darren Hart
2012-03-26 13:53 ` [PATCH 0/1] [linux-yocto-3.2][meta] " Bruce Ashfield

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=cover.1332539317.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=sgw@linux.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.