All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 1/2] linux-yocto/meta-yocto: create linux-yocto 3.2 bbappend
Date: Tue, 31 Jan 2012 11:21:31 -0500	[thread overview]
Message-ID: <4F28150B.30001@windriver.com> (raw)
In-Reply-To: <4F28146E.10104@linux.intel.com>

On 12-01-31 11:18 AM, Darren Hart wrote:
>
>
> On 01/30/2012 12:16 PM, Bruce Ashfield wrote:
>> Now that the 3.2 kernel has been introduced, we need a 3.2 bbappend for
>> the yocto hardware reference boards.
>>
>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
>> ---
>>   .../recipes-kernel/linux/linux-yocto_3.2.bbappend  |   19 +++++++++++++++++++
>>   1 files changed, 19 insertions(+), 0 deletions(-)
>>   create mode 100644 meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
>>
>> diff --git a/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend b/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> new file mode 100644
>> index 0000000..5e25910
>> --- /dev/null
>> +++ b/meta-yocto/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> @@ -0,0 +1,19 @@
>> +KMACHINE_atom-pc  = "atom-pc"
>> +KMACHINE_routerstationpro = routerstationpro"
>> +KMACHINE_mpc8315e-rdb = "fsl-mpc8315e-rdb"
>> +KMACHINE_beagleboard = "beagleboard"
>> +
>> +KBRANCH_atom-pc  = "standard/default/common-pc/atom-pc"
>> +KBRANCH_routerstationpro = "standard/default/routerstationpro"
>> +KBRANCH_mpc8315e-rdb = "standard/default/fsl-mpc8315e-rdb"
>> +KBRANCH_beagleboard = "standard/default/beagleboard"
>
> Do all of these machines still have BSP-specific patches which require
> their own branch?

beagleboard and routerstation pro .. yes.
atom-pc. It is historical so I left it be for now.
the fsl board. yes, there will be as well.

Cheers,

Bruce

>
> --
> Darren
>
>> +
>> +SRCREV_machine_atom-pc ?= "417fc778a86e81303bab5883b919ee422ec51c04"
>> +SRCREV_machine_routerstationpro ?= "e015d29f374cd986e15f636b6b84b514d95d76ed"
>> +SRCREV_machine_mpc8315e-rdb ?= "2349967f408cc60db2b1c89fcefffc81428f9341"
>> +SRCREV_machine_beagleboard ?= "417fc778a86e81303bab5883b919ee422ec51c04"
>> +
>> +COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>> +COMPATIBLE_MACHINE_routerstationpro = "routerstationpro"
>> +COMPATIBLE_MACHINE_beagleboard = "beagleboard"
>> +COMPATIBLE_MACHINE_atom-pc = "atom-pc"
>



  reply	other threads:[~2012-01-31 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 20:16 [PATCH 0/2] linux-yocto/meta-yocto: 3.2.2 and 3.0.18 Bruce Ashfield
2012-01-30 20:16 ` [PATCH 1/2] linux-yocto/meta-yocto: create linux-yocto 3.2 bbappend Bruce Ashfield
2012-01-31 16:18   ` Darren Hart
2012-01-31 16:21     ` Bruce Ashfield [this message]
2012-01-30 20:16 ` [PATCH 2/2] meta-yocto/poky.conf: set qemu* preferred linux-yocto version to 3.2 Bruce Ashfield
2012-01-30 20:35   ` Khem Raj
2012-01-30 20:36     ` Bruce Ashfield
2012-01-30 20:18 ` [PATCH 0/2] linux-yocto/meta-yocto: 3.2.2 and 3.0.18 Bruce Ashfield
2012-02-02 17:54 ` Saul Wold

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=4F28150B.30001@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@intel.com \
    /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.