[meta-intel] [PATCH 0/1] intel-common README

[Darren Hart]

On 3/10/14, 23:32, "Ong, Boon Leong" <boon.leong.ong at intel.com> wrote:

>
>
>> -----Original Message-----
>> From: Darren Hart [mailto:dvhart at linux.intel.com]
>> Sent: Tuesday, March 11, 2014 5:20 AM
>> To: Meta Intel; Ong, Boon Leong; Kamble, Nitin A; Zanussi, Tom; Chan,
>>Wei Sern
>> Subject: [PATCH 0/1] intel-common README
>> 
>> This is a quick attempt at a README for the intel-common BSPs. Nothing
>>formal,
>> but it gets the idea and concept out there. Please review that you are
>>in
>> agreement with the wording, and especially that you are OK with your
>>BSPs
>> being listed under the compatible intel-common BSP.
>
>I wonder whether it will be easier for user to read about this content at
>meta-intel/README?
>Or, we can make it apparent that the existence of intel-common README at
>meta-intel/conf/
>machine by adding a pointer from meta-intel/README.

Good point, I'll have a look and see which makes the most sense.

>
>I am ok for all the ISG-maintained BSPs to be listed here.
>After intel-common has stabilze, we plan to start moving all of these
>BSPs into meta-isg, add
>a note to describe about SRCREV control in-place.

And to make sure we are all on the same page here. You are talking about
setting a SRCREV for machine and meta that ISG has validated, but still
use standard/base whenever possible, and still use intel-common-pkgarch?
What would be ideal is if meta-isg had a single linux-yocto bbappend to
override these two for all the BSPs that used intel-common-pkgarch:

meta-isg/recipes-kernel/linux/linux-yocto_3.10.bbappend

This will reduce the number of different sources ISG supports and also
maximize the amount of build-artifact reuse on our and your auto builders.
It maintains the goals of the intel-common Linux kernel package
architecture, while maintaining a known validated source for ISG.

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