[yocto] [PATCH] routerstationpro: move board off 3.0 and onto the 3.4 kernel

[Darren Hart]

On 08/17/2012 06:36 AM, Paul Gortmaker wrote:
> On 12-08-16 06:27 PM, Saul Wold wrote:
>> On 07/27/2012 10:10 AM, Paul Gortmaker wrote:
>>> The updated patch series to support this target is in place
>>> on the BSP specific branch in the 3.4 kernel tree now[1], so
>>> we can move it ahead off of the old 3.0 kernel.
>>>
>>> [1] https://lists.yoctoproject.org/pipermail/linux-yocto/2012-July/000023.html
>>>
>>> Signed-off-by: Paul Gortmaker <paul.gortmaker at windriver.com>
>>>
>>> diff --git a/meta-yocto/conf/machine/routerstationpro.conf b/meta-yocto/conf/machine/routerstationpro.conf
>>> index 3c2f56f..adf36a9 100644
>>> --- a/meta-yocto/conf/machine/routerstationpro.conf
>>> +++ b/meta-yocto/conf/machine/routerstationpro.conf
>>> @@ -10,7 +10,7 @@ KERNEL_IMAGETYPE = "vmlinux"
>>>   KERNEL_ALT_IMAGETYPE = "vmlinux.bin"
>>>
>>>   PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>>> -PREFERRED_VERSION_linux-yocto ?= "3.0%"
>>> +PREFERRED_VERSION_linux-yocto ?= "3.4%"
>>>   PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive"
>>>   XSERVER = "xserver-kdrive-fbdev"
>>>
>>> diff --git a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend
>>> index 2ff467b..1c8d26a 100644
>>> --- a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend
>>> +++ b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend
>>> @@ -4,11 +4,11 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
>>>   KBRANCH_beagleboard = "standard/beagleboard"
>>>
>>>   SRCREV_machine_atom-pc ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
>>> -SRCREV_machine_routerstationpro ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
>>> +SRCREV_machine_routerstationpro ?= "27019633ccdaa88dc55101615d936d1d74db9a1e"
>>>   SRCREV_machine_mpc8315e-rdb ?= "47d3076aa7e2a640a1dab8d663529a784709f697"
>>>   SRCREV_machine_beagleboard ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72"
>>>
>>>   COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>>> -# COMPATIBLE_MACHINE_routerstationpro = "routerstationpro"
>>> +COMPATIBLE_MACHINE_routerstationpro = "routerstationpro"
>>>   # COMPATIBLE_MACHINE_beagleboard = "beagleboard"
>>>   COMPATIBLE_MACHINE_atom-pc = "atom-pc"
>>>
>>
>> Yup, this got lost, sorry about that.  It will need to be rebased 
>> against the patchset that Bruce put up, as I am working with that set also.
> 
> I'll resend with the latest SRCREV.  Too bad SRCREV="latest" isn't
> the default, it would save a lot of churn, at least in dev cycles
> where there is no excuse for not wanting the latest...


I hear you on this, unfortunately the problem with using anything other
than specific commit ids is that they require a network lookup :-(


>> Also, changes to meta-yocto should go to poky at yoctoproject.org.
> 
> Is there something akin to a maintainers file or similar that
> adds some clarity as to what goes where?  I'm looking at the
> list summaries here:  https://lists.yoctoproject.org/  and it
> isn't helping me understand what bits I should send where.
> 

A continual source of confusion unfortunately. But you're right, I don't
see anything in poky or meta-yocto that state where the patches should
be sent like other layers do with README or MAINTAINERS.

I've sent a patch to that effect.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel