From: Darren Hart <dvhart@linux.intel.com>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/1] meta-sugarbay: switch to linux-yocto-3.2 kernel
Date: Tue, 13 Mar 2012 12:31:11 -0700 [thread overview]
Message-ID: <4F5FA07F.2080102@linux.intel.com> (raw)
In-Reply-To: <e7f7340ffd113656aaa77825207dfdeda607de01.1331646257.git.tom.zanussi@intel.com>
Same comments on branch and SRCREV here as for crownbay.
On 03/13/2012 06:47 AM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> Switch sugarbay to the 3.2 kernel and update kernel SRCREVs.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> meta-sugarbay/conf/machine/sugarbay.conf | 2 ++
> .../linux/linux-yocto-rt_3.2.bbappend | 8 ++++++++
> .../recipes-kernel/linux/linux-yocto_3.2.bbappend | 9 +++++++++
> 3 files changed, 19 insertions(+), 0 deletions(-)
> create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>
> diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
> index 25b3aad..776089e 100644
> --- a/meta-sugarbay/conf/machine/sugarbay.conf
> +++ b/meta-sugarbay/conf/machine/sugarbay.conf
> @@ -4,6 +4,8 @@
> #@DESCRIPTION: Machine configuration for Sugar Bay systems
> # i.e. Sandy Bridge + Cougar Point
>
> +PREFERRED_VERSION_linux-yocto ?= "3.2%"
> +
> require conf/machine/include/tune-x86_64.inc
> require conf/machine/include/ia32-base.inc
>
> diff --git a/meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend b/meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> new file mode 100644
> index 0000000..531a3ad
> --- /dev/null
> +++ b/meta-sugarbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> @@ -0,0 +1,8 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +COMPATIBLE_MACHINE_sugarbay = "sugarbay"
> +KMACHINE_sugarbay = "sugarbay"
> +
> +# Update the following to use a different BSP branch or meta SRCREV
> +#KBRANCH_sugarbay = "standard/preempt-rt/base"
> +#SRCREV_machine_pn-linux-yocto-rt_sugarbay ?= XXXX
> +#SRCREV_meta_pn-linux-yocto-rt_sugarbay ?= XXXX
> diff --git a/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
> new file mode 100644
> index 0000000..4755fa7
> --- /dev/null
> +++ b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
> @@ -0,0 +1,9 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +COMPATIBLE_MACHINE_sugarbay = "sugarbay"
> +
> +KMACHINE_sugarbay = "sugarbay"
> +KBRANCH_sugarbay = "standard/default/common-pc-64/sugarbay"
> +
> +SRCREV_machine_pn-linux-yocto_sugarbay ?= "6b0da62eb4beaf950ef235cb548490afe6cfd055"
> +SRCREV_meta_pn-linux-yocto_sugarbay ?= "64840f55ee144e9814278eaa8e3f33dd60da892c"
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2012-03-13 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 13:47 [PATCH 0/1] meta-intel: sugarbay 3.2 update tom.zanussi
2012-03-13 13:47 ` [PATCH 1/1] meta-sugarbay: switch to linux-yocto-3.2 kernel tom.zanussi
2012-03-13 19:31 ` Darren Hart [this message]
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=4F5FA07F.2080102@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=tom.zanussi@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.