Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-29 Thread Darren Hart


On 7/29/15 12:02 PM, Darren Hart wrote:
 
 
 On 7/28/15 2:22 PM, Darren Hart wrote:


 On 7/23/15 3:00 PM, Ross Burton wrote:
 From: Bruce Ashfield bruce.ashfi...@windriver.com

 Now that the BSP meta data comes from a separate git repository, we
 need to update the meta SRCREVs to ones that are valid in that tree
 (the previous REVs are only valid in a linux-yocto meta branch).

 Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com

 Merged,

 Thanks Ross/Bruce.
 
 So I'm seeing a build failure, unable to fetch meta for 3.14. Are we
 missing something in the meta-intel bbappends to take advantage of the
 external meta?

Nevermind, PEBKAC

-- 
Darren Hart
Intel Open Source Technology Center
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-24 Thread Darren Hart
On 7/23/15, 3:59 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote:

On 2015-07-23 6:56 PM, Burton, Ross wrote:

 On 23 July 2015 at 23:45, Bruce Ashfield bruce.ashfi...@windriver.com
 mailto:bruce.ashfi...@windriver.com wrote:

 This is only master, and the first tree with no meta branch is
 the 4.1 kernel tree.

 Existing branches, with their kernel trees, and tools continue to
 work as they were.


 Either it's late (it is) or I'm being dumb (quite likely), but why did
 we need to fix the 3.19 srvrevs if it only impacts 4.1 kernels?

Because the SRC_URI of the main recipe in master now points the
meta name at yocto-kernel-cache (as does 3.14). I needed to do
that, so I could remove the dead code from the tools and put that
into master.

Some of the main goals here was to reduce complexity, and promote
the sharing of the fragments. So the old stuff goes to the bin :)

How will this affect the meta branch of the older kernels in terms of
receiving updates that the previous releases, without the infrastructure
for the yocto-kernel-cache, can use? Are you going to apply changes to
both the old meta branch as well as the new repository until fido is EOL?


-- 
Darren Hart
Intel Open Source Technology Center



-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-24 Thread Bruce Ashfield

On 15-07-24 12:13 PM, Darren Hart wrote:

On 7/23/15, 3:59 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote:


On 2015-07-23 6:56 PM, Burton, Ross wrote:


On 23 July 2015 at 23:45, Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com wrote:

 This is only master, and the first tree with no meta branch is
 the 4.1 kernel tree.

 Existing branches, with their kernel trees, and tools continue to
 work as they were.


Either it's late (it is) or I'm being dumb (quite likely), but why did
we need to fix the 3.19 srvrevs if it only impacts 4.1 kernels?


Because the SRC_URI of the main recipe in master now points the
meta name at yocto-kernel-cache (as does 3.14). I needed to do
that, so I could remove the dead code from the tools and put that
into master.

Some of the main goals here was to reduce complexity, and promote
the sharing of the fragments. So the old stuff goes to the bin :)


How will this affect the meta branch of the older kernels in terms of
receiving updates that the previous releases, without the infrastructure
for the yocto-kernel-cache, can use? Are you going to apply changes to
both the old meta branch as well as the new repository until fido is EOL?


Yep. I just apply changes to the meta branches, and update the SRCREVs
in existing branches, just as I always did.

I always apply changes to both the linux-yocto meta branch and the
kernel-cache, so if that same kernel recipe was used in master, the
result is the same.

Bruce






--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Bruce Ashfield

On 2015-07-23 6:44 PM, Darren Hart wrote:

On 7/23/15 3:38 PM, Bruce Ashfield wrote:

On 2015-07-23 6:35 PM, Darren Hart wrote:

Hrm,

What does this apply against?


You need the patches that I sent to oe-core that split the meta data
from the kernel repository (see zedd/kernel in poky-contrib).

The revs must exist in the yocto-kernel-cache repository. It's a
chicken and egg situation. This broke under test when my series is
applied, but can't merge until that series goes into oe-core.



Thanks, somehow I had no idea this was happening. This will need to be
updated in the kernel-dev manual.

Does this also impact previous releases? fido, dizzy, dora, ... ?


Nope. Only master. I'm not removing the meta branch from those
trees, or updating the tools.

This is only master, and the first tree with no meta branch is
the 4.1 kernel tree.

Existing branches, with their kernel trees, and tools continue to
work as they were.

Bruce





--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Bruce Ashfield

On 2015-07-23 6:35 PM, Darren Hart wrote:

Hrm,

What does this apply against?


You need the patches that I sent to oe-core that split the meta data
from the kernel repository (see zedd/kernel in poky-contrib).

The revs must exist in the yocto-kernel-cache repository. It's a
chicken and egg situation. This broke under test when my series is
applied, but can't merge until that series goes into oe-core.

Bruce



WARNING: Failed to fetch URL
git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=standard/base,meta;name=machine,meta,
attempting MIRRORS if available
ERROR: Fetcher failure: Unable to find revision
7a562420b2061216ca7e2dd2195238d51851b9fe in branch meta even from upstream
ERROR: Function failed: Fetcher failure for URL:
'git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=standard/base,meta;name=machine,meta'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/build/yocto/master/intel-corei7-64_20141008094748/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.19.5+gitAUTOINC+7a562420b2_e152349de5-r0/temp/log.do_fetch.32282
ERROR: Task 6
(/build/yocto/master/intel-corei7-64_20141008094748/poky/meta/recipes-kernel/linux/linux-yocto_3.19.bb,
do_fetch) failed with exit code '1'

On 7/23/15 3:00 PM, Ross Burton wrote:

From: Bruce Ashfield bruce.ashfi...@windriver.com

Now that the BSP meta data comes from a separate git repository, we
need to update the meta SRCREVs to ones that are valid in that tree
(the previous REVs are only valid in a linux-yocto meta branch).

Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
  common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend| 4 ++--
  common/recipes-kernel/linux/linux-yocto_3.14.bbappend   | 4 ++--
  common/recipes-kernel/linux/linux-yocto_3.19.bbappend   | 4 ++--
  meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend | 2 +-
  4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend 
b/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
index a0b4315..dbf6841 100644
--- a/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
+++ b/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
@@ -2,7 +2,7 @@ FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:

  LINUX_VERSION_core2-32-intel-common = 3.14.36
  COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
-SRCREV_meta_core2-32-intel-common = 162dfe3bb092c1a792e5ed224fe09672e9814b24
+SRCREV_meta_core2-32-intel-common = c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_core2-32-intel-common = 
3fb54cf8f4c3254f628e6c4720fe3c731a9de0b2
  KMACHINE_core2-32-intel-common = intel-core2-32
  KBRANCH_core2-32-intel-common = standard/preempt-rt/base
@@ -10,7 +10,7 @@ KERNEL_FEATURES_append_core2-32-intel-common = 
${KERNEL_FEATURES_INTEL_COMMON}

  LINUX_VERSION_corei7-64-intel-common = 3.14.36
  COMPATIBLE_MACHINE_corei7-64-intel-common = ${MACHINE}
-SRCREV_meta_corei7-64-intel-common = 162dfe3bb092c1a792e5ed224fe09672e9814b24
+SRCREV_meta_corei7-64-intel-common = c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_corei7-64-intel-common = 
3fb54cf8f4c3254f628e6c4720fe3c731a9de0b2
  KMACHINE_corei7-64-intel-common = intel-corei7-64
  KBRANCH_corei7-64-intel-common = standard/preempt-rt/base
diff --git a/common/recipes-kernel/linux/linux-yocto_3.14.bbappend 
b/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
index 01775b7..2407e86 100644
--- a/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
+++ b/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
@@ -5,7 +5,7 @@ KERNEL_FEATURES_INTEL_COMMON += features/amt/mei/mei.scc

  LINUX_VERSION_core2-32-intel-common = 3.14.39
  COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
-SRCREV_meta_core2-32-intel-common = a996d95104b72c422a56e7d9bc8615ec4219ac74
+SRCREV_meta_core2-32-intel-common = c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_core2-32-intel-common = 
bda175966009d5a94103559e6e6ae51279952f39
  KMACHINE_core2-32-intel-common = intel-core2-32
  KBRANCH_core2-32-intel-common = standard/base
@@ -13,7 +13,7 @@ KERNEL_FEATURES_append_core2-32-intel-common = 
${KERNEL_FEATURES_INTEL_COMMON}

  LINUX_VERSION_corei7-64-intel-common = 3.14.39
  COMPATIBLE_MACHINE_corei7-64-intel-common = ${MACHINE}
-SRCREV_meta_corei7-64-intel-common = a996d95104b72c422a56e7d9bc8615ec4219ac74
+SRCREV_meta_corei7-64-intel-common = c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_corei7-64-intel-common = 
bda175966009d5a94103559e6e6ae51279952f39
  KMACHINE_corei7-64-intel-common = intel-corei7-64
  KBRANCH_corei7-64-intel-common = standard/base
diff --git a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend 
b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
index a0f0e34..a074be0 100644
--- a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
+++ b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
@@ -5,7 +5,7 @@ KERNEL_FEATURES_INTEL_COMMON += 

Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Darren Hart
On 7/23/15 3:38 PM, Bruce Ashfield wrote:
 On 2015-07-23 6:35 PM, Darren Hart wrote:
 Hrm,

 What does this apply against?
 
 You need the patches that I sent to oe-core that split the meta data
 from the kernel repository (see zedd/kernel in poky-contrib).
 
 The revs must exist in the yocto-kernel-cache repository. It's a
 chicken and egg situation. This broke under test when my series is
 applied, but can't merge until that series goes into oe-core.
 

Thanks, somehow I had no idea this was happening. This will need to be
updated in the kernel-dev manual.

Does this also impact previous releases? fido, dizzy, dora, ... ?

-- 
Darren Hart
Intel Open Source Technology Center
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Burton, Ross
On 23 July 2015 at 23:38, Bruce Ashfield bruce.ashfi...@windriver.com
wrote:

 You need the patches that I sent to oe-core that split the meta data
 from the kernel repository (see zedd/kernel in poky-contrib).

 The revs must exist in the yocto-kernel-cache repository. It's a
 chicken and egg situation. This broke under test when my series is
 applied, but can't merge until that series goes into oe-core.


For now, I pushed a branch to meta-intel-contrib (ross/kernel) that has
this patch for testing with oe-core master-next.  Obviously the actual
merge to oe-core and meta-intel needs to be orchestrated somehow so there's
not a several day lag between the commits.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Bruce Ashfield

On 2015-07-23 6:56 PM, Burton, Ross wrote:


On 23 July 2015 at 23:45, Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com wrote:

This is only master, and the first tree with no meta branch is
the 4.1 kernel tree.

Existing branches, with their kernel trees, and tools continue to
work as they were.


Either it's late (it is) or I'm being dumb (quite likely), but why did
we need to fix the 3.19 srvrevs if it only impacts 4.1 kernels?


Because the SRC_URI of the main recipe in master now points the
meta name at yocto-kernel-cache (as does 3.14). I needed to do
that, so I could remove the dead code from the tools and put that
into master.

Some of the main goals here was to reduce complexity, and promote
the sharing of the fragments. So the old stuff goes to the bin :)

Bruce



Ross


--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel


Re: [meta-intel] [PATCH] bsps: update meta SRCREVs

2015-07-23 Thread Darren Hart
Hrm,

What does this apply against?

WARNING: Failed to fetch URL
git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=standard/base,meta;name=machine,meta,
attempting MIRRORS if available
ERROR: Fetcher failure: Unable to find revision
7a562420b2061216ca7e2dd2195238d51851b9fe in branch meta even from upstream
ERROR: Function failed: Fetcher failure for URL:
'git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=standard/base,meta;name=machine,meta'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/build/yocto/master/intel-corei7-64_20141008094748/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.19.5+gitAUTOINC+7a562420b2_e152349de5-r0/temp/log.do_fetch.32282
ERROR: Task 6
(/build/yocto/master/intel-corei7-64_20141008094748/poky/meta/recipes-kernel/linux/linux-yocto_3.19.bb,
do_fetch) failed with exit code '1'

On 7/23/15 3:00 PM, Ross Burton wrote:
 From: Bruce Ashfield bruce.ashfi...@windriver.com
 
 Now that the BSP meta data comes from a separate git repository, we
 need to update the meta SRCREVs to ones that are valid in that tree
 (the previous REVs are only valid in a linux-yocto meta branch).
 
 Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
 ---
  common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend| 4 ++--
  common/recipes-kernel/linux/linux-yocto_3.14.bbappend   | 4 ++--
  common/recipes-kernel/linux/linux-yocto_3.19.bbappend   | 4 ++--
  meta-emenlow/recipes-kernel/linux/linux-yocto_3.14.bbappend | 2 +-
  4 files changed, 7 insertions(+), 7 deletions(-)
 
 diff --git a/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend 
 b/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
 index a0b4315..dbf6841 100644
 --- a/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
 +++ b/common/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend
 @@ -2,7 +2,7 @@ FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
  
  LINUX_VERSION_core2-32-intel-common = 3.14.36
  COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
 -SRCREV_meta_core2-32-intel-common = 
 162dfe3bb092c1a792e5ed224fe09672e9814b24
 +SRCREV_meta_core2-32-intel-common = 
 c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_core2-32-intel-common = 
 3fb54cf8f4c3254f628e6c4720fe3c731a9de0b2
  KMACHINE_core2-32-intel-common = intel-core2-32
  KBRANCH_core2-32-intel-common = standard/preempt-rt/base
 @@ -10,7 +10,7 @@ KERNEL_FEATURES_append_core2-32-intel-common = 
 ${KERNEL_FEATURES_INTEL_COMMON}
  
  LINUX_VERSION_corei7-64-intel-common = 3.14.36
  COMPATIBLE_MACHINE_corei7-64-intel-common = ${MACHINE}
 -SRCREV_meta_corei7-64-intel-common = 
 162dfe3bb092c1a792e5ed224fe09672e9814b24
 +SRCREV_meta_corei7-64-intel-common = 
 c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_corei7-64-intel-common = 
 3fb54cf8f4c3254f628e6c4720fe3c731a9de0b2
  KMACHINE_corei7-64-intel-common = intel-corei7-64
  KBRANCH_corei7-64-intel-common = standard/preempt-rt/base
 diff --git a/common/recipes-kernel/linux/linux-yocto_3.14.bbappend 
 b/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
 index 01775b7..2407e86 100644
 --- a/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
 +++ b/common/recipes-kernel/linux/linux-yocto_3.14.bbappend
 @@ -5,7 +5,7 @@ KERNEL_FEATURES_INTEL_COMMON += features/amt/mei/mei.scc
  
  LINUX_VERSION_core2-32-intel-common = 3.14.39
  COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
 -SRCREV_meta_core2-32-intel-common = 
 a996d95104b72c422a56e7d9bc8615ec4219ac74
 +SRCREV_meta_core2-32-intel-common = 
 c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_core2-32-intel-common = 
 bda175966009d5a94103559e6e6ae51279952f39
  KMACHINE_core2-32-intel-common = intel-core2-32
  KBRANCH_core2-32-intel-common = standard/base
 @@ -13,7 +13,7 @@ KERNEL_FEATURES_append_core2-32-intel-common = 
 ${KERNEL_FEATURES_INTEL_COMMON}
  
  LINUX_VERSION_corei7-64-intel-common = 3.14.39
  COMPATIBLE_MACHINE_corei7-64-intel-common = ${MACHINE}
 -SRCREV_meta_corei7-64-intel-common = 
 a996d95104b72c422a56e7d9bc8615ec4219ac74
 +SRCREV_meta_corei7-64-intel-common = 
 c33d39561807e1073ca412f1c771f43e4da75994
  SRCREV_machine_corei7-64-intel-common = 
 bda175966009d5a94103559e6e6ae51279952f39
  KMACHINE_corei7-64-intel-common = intel-corei7-64
  KBRANCH_corei7-64-intel-common = standard/base
 diff --git a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend 
 b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
 index a0f0e34..a074be0 100644
 --- a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
 +++ b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
 @@ -5,7 +5,7 @@ KERNEL_FEATURES_INTEL_COMMON += features/amt/mei/mei.scc
  
  LINUX_VERSION_core2-32-intel-common = 3.19.5
  COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
 -SRCREV_meta_core2-32-intel-common = 
 913358acd0e27f274c96da7d699e2d18b2c9ee27
 +SRCREV_meta_core2-32-intel-common = 
 7a562420b2061216ca7e2dd2195238d51851b9fe
  SRCREV_machine_core2-32-intel-common =