[PATCH 0/2] kernel: 3.19 updates and tools tweak

[PATCH 0/2] kernel: 3.19 updates and tools tweak

[Bruce Ashfield]

Richard,

Here are a couple of change that just missed the 1.8 cut off, so I'm sending
them out now .. before I send my queue with the new 4.x kernels, and LTSI/stable
updates for all the trees.

The tools change addresses [YOCTO: #7441], and makes the detection of meta
data simpler, and also smarter, so random directories in the source tree
won't break things.

The 3.19 update is a stable integration and some configuration changes that
are requied for Bluetooth (along wit some other board tweaks). I've built and
booted on the qemu machines for this update.

Cheers,

Bruce


The following changes since commit 203aaaec084b80d0146b379d00527f8bd08b4119:

  bitbake: bitbake-user-manual: Cleaned up parallelism note and formatted user input (2015-04-17 13:28:47 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (2):
  kern-tools: unify meta directory detection
  linux-yocto/3.19: configuration updates and stable integration

 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.19.bb        | 20 ++++++++++----------
 3 files changed, 14 insertions(+), 14 deletions(-)

-- 
2.1.0

[PATCH 1/2] kern-tools: unify meta directory detection

[Bruce Ashfield]

It is possible that recipe specific tasks, or build processes drop
files into the kernel source directory. These files can cause problems
with the meta data detection in the kern-tools.

With this change, we have a single unified meta data detection routine,
that logs the result in a new file ".metadir", which subsequent scripts
can find, and use, thereby avoid repeating the same check many times.

We also enhance the check to look for a sentinel file in a proper meta
directory, to avoid false positives when an unexpected kernel process
leaves an uncommitted directory in the kernel dir.

[YOCTO: #7441]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index a1ec198fde7f..e83f195a5393 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
 
 DEPENDS = "git-native"
 
-SRCREV = "83e5493ea46067152609008ade131971eaebbb27"
+SRCREV = "79bc82453c26d426d3d8fd05d5da37cf5fc4068c"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.1.0

Re: [PATCH 1/2] kern-tools: unify meta directory detection

[Richard Purdie]

On Fri, 2015-04-24 at 12:13 -0400, Bruce Ashfield wrote:
> It is possible that recipe specific tasks, or build processes drop
> files into the kernel source directory. These files can cause problems
> with the meta data detection in the kern-tools.
> 
> With this change, we have a single unified meta data detection routine,
> that logs the result in a new file ".metadir", which subsequent scripts
> can find, and use, thereby avoid repeating the same check many times.
> 
> We also enhance the check to look for a sentinel file in a proper meta
> directory, to avoid false positives when an unexpected kernel process
> leaves an uncommitted directory in the kernel dir.
> 
> [YOCTO: #7441]
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index a1ec198fde7f..e83f195a5393 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
>  
>  DEPENDS = "git-native"
>  
> -SRCREV = "83e5493ea46067152609008ade131971eaebbb27"
> +SRCREV = "79bc82453c26d426d3d8fd05d5da37cf5fc4068c"
>  PR = "r12"
>  PV = "0.2+git${SRCPV}"

There is no such revision in the repo? The test builds all failed...

Cheers,

Richard

Re: [PATCH 1/2] kern-tools: unify meta directory detection

[Bruce Ashfield]

On 2015-04-27 05:18 AM, Richard Purdie wrote:
> On Fri, 2015-04-24 at 12:13 -0400, Bruce Ashfield wrote:
>> It is possible that recipe specific tasks, or build processes drop
>> files into the kernel source directory. These files can cause problems
>> with the meta data detection in the kern-tools.
>>
>> With this change, we have a single unified meta data detection routine,
>> that logs the result in a new file ".metadir", which subsequent scripts
>> can find, and use, thereby avoid repeating the same check many times.
>>
>> We also enhance the check to look for a sentinel file in a proper meta
>> directory, to avoid false positives when an unexpected kernel process
>> leaves an uncommitted directory in the kernel dir.
>>
>> [YOCTO: #7441]
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>>   meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> index a1ec198fde7f..e83f195a5393 100644
>> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
>>
>>   DEPENDS = "git-native"
>>
>> -SRCREV = "83e5493ea46067152609008ade131971eaebbb27"
>> +SRCREV = "79bc82453c26d426d3d8fd05d5da37cf5fc4068c"
>>   PR = "r12"
>>   PV = "0.2+git${SRCPV}"
>
> There is no such revision in the repo? The test builds all failed...

what ? I made that change ages ago .. I wonder if I squirreled
it away on a branch.

I should just remember to never send changes on Friday.

Fixed now.

Bruce

>
> Cheers,
>
> Richard
>
>
>

[PATCH 2/2] linux-yocto/3.19: configuration updates and stable integration

[Bruce Ashfield]

Bumping the linux-yocto 3.19 SRCREVs to integrate the 3.19.5 korg
stable updates, as well as the following meta data changes:

  205aca0c1241 meta: intel-common: Enable USB-based Bluetooth hardware
  b6a810e8e808 meta: features/bluetooth: add support for USB Bluetooth hardware
  767f3fa34680 common-pc-drivers: Add CONFIG_EEPROM_AT24
  e308b2c52519 intel-core*: Add Braswell soc support
  8c1c74d5052b braswell: Add features/soc/braswell

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 20 ++++++++++----------
 2 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
index 0631c5e55156..15fc536e0a41 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "3.19.2"
+LINUX_VERSION ?= "3.19.5"
 
 KMETA = "meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
+SRCREV_machine ?= "d5d30ba4d20e65c15df624ffce7a5cd38150348b"
+SRCREV_meta ?= "1b28e65444c0da26c347eba6272984547ab4983b"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.19.bb b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
index 9b19eb299b16..e47e22b39695 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
@@ -11,19 +11,19 @@ KBRANCH_qemux86  ?= "standard/common-pc"
 KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "473e2f3788730c51e82714a9785325b6308f6762"
-SRCREV_machine_qemuarm64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_machine_qemumips ?= "d43f1cbf282d020f7aa31d68a54b2876d2c0e81b"
-SRCREV_machine_qemuppc ?= "35de413056b86191963ffe686913da31b978a9b3"
-SRCREV_machine_qemux86 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_machine_qemux86-64 ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_machine_qemumips64 ?= "d35649ef8cbb0a0404be5c721377b138866181ad"
-SRCREV_machine ?= "31b35da6a5c8a2b162f6c33202e9b64dd13757d5"
-SRCREV_meta ?= "9e70b482d3773abf92c9c5850e134cbca1d5651f"
+SRCREV_machine_qemuarm ?= "4f9b327ff33521c08ed279891e2a2099b5504d0e"
+SRCREV_machine_qemuarm64 ?= "d5d30ba4d20e65c15df624ffce7a5cd38150348b"
+SRCREV_machine_qemumips ?= "03b975caa49e6e1693d6fe5fec8f316e0481ead5"
+SRCREV_machine_qemuppc ?= "9a3edc9c341e6f57423f2b4b218b83a84fc2726d"
+SRCREV_machine_qemux86 ?= "d5d30ba4d20e65c15df624ffce7a5cd38150348b"
+SRCREV_machine_qemux86-64 ?= "d5d30ba4d20e65c15df624ffce7a5cd38150348b"
+SRCREV_machine_qemumips64 ?= "f631de1c3df29a85a4b882acf19682fe05eec0f3"
+SRCREV_machine ?= "d5d30ba4d20e65c15df624ffce7a5cd38150348b"
+SRCREV_meta ?= "1b28e65444c0da26c347eba6272984547ab4983b"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
 
-LINUX_VERSION ?= "3.19.2"
+LINUX_VERSION ?= "3.19.5"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.1.0