From: tom.zanussi@intel.com
To: yocto@yoctoproject.org, bruce.ashfield@windriver.com
Subject: [PATCH 0/2][KERNEL] new chiefriver BSP metadata
Date: Fri, 25 May 2012 16:48:50 -0500 [thread overview]
Message-ID: <cover.1337981191.git.tom.zanussi@intel.com> (raw)
From: Tom Zanussi <tom.zanussi@intel.com>
This patchset implements the initial kernel side of the chiefriver
BSP.
It also adds a 'temporary' feature needed for turning on rc6 support
from recipe-space. The code contained in the rc6 feature is already
upstream and this feature will be dropped in the next yocto kernel,
but is needed for now in 3.2 - this is the most flexible way to add
it while giving ourselves an easy way to drop it if it causes
problems.
Please pull into linux-yocto 3.2, and also create a new
standard/default/common-pc-64/chiefriver branch for it.
Thanks,
Tom
The following changes since commit 49f931bc294d5b6be60502bbd448cff5aa766235:
Tom Zanussi (1):
meta/fishriver: remove redundant features and options
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/chiefriver.v2
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/chiefriver.v2
Tom Zanussi (2):
chiefriver: create initial BSP infrastructure
meta: add tmp/rc6 feature
.../bsp/chiefriver/chiefriver-preempt-rt.scc | 12 +++
.../bsp/chiefriver/chiefriver-standard.scc | 11 +++
.../cfg/kernel-cache/bsp/chiefriver/chiefriver.cfg | 35 +++++++++
.../cfg/kernel-cache/bsp/chiefriver/chiefriver.scc | 7 ++
.../features/tmp/rc6/rc6-kernel-params.patch | 81 ++++++++++++++++++++
meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc | 5 +
.../tmp/rc6/snb-disable-rc6p-fix-precedence.patch | 26 ++++++
.../features/tmp/rc6/snb-disable-rc6p.patch | 39 ++++++++++
.../features/tmp/rc6/snb-enable-rc6.patch | 54 +++++++++++++
9 files changed, 270 insertions(+), 0 deletions(-)
create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver-preempt-rt.scc
create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver-standard.scc
create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver.cfg
create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver.scc
create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch
create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch
create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch
next reply other threads:[~2012-05-25 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 21:48 tom.zanussi [this message]
2012-05-25 21:48 ` [PATCH 1/2][KERNEL] chiefriver: create initial BSP infrastructure tom.zanussi
2012-05-25 21:48 ` [PATCH 2/2][KERNEL] meta: add tmp/rc6 feature tom.zanussi
2012-05-28 20:23 ` [PATCH 0/2][KERNEL] new chiefriver BSP metadata Bruce Ashfield
2012-05-29 20:19 ` 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.1337981191.git.tom.zanussi@intel.com \
--to=tom.zanussi@intel.com \
--cc=bruce.ashfield@windriver.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.