[PATCH 0/5] linux-yocto: consolidated pull request

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Richard/Saul,

Since this is a stabilization week, this probably can't be merged
immediately, but I've been working with this enough to call it
good enough, and me sitting on them longer doesn't help.

The first change in this series is the switch of qemuppc from prep to
mac99. With this, we'll close a whole set of issues (slow bootup) and
close a feature gap that has existed for a while.

I'm seeing a bit of strangeness with the mouse in my sato testing,
but that's about it. Liming hasn't seen the same issues, so getting
this into the tree will allow us to incrementally improve and debug
this.

The second change is a SRCREV update pulls in the forward looking
fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
that was found on the routerstationpro.

Cheers,

Bruce

cc: Khem Raj <raj.khem@gmail.com>
cc: Zumeng Chen <zumeng.chen@windriver.com>
cc: Liming Wang <liming.wang@windriver.com>

The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:

  package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)

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 (1):
  linux-yocto: consolidated fix SRCREV updates

Liming Wang (4):
  qemuppc: replace emulation of qemuppc from prep to mac99
  qemuppc: add pointercal file
  qemuppc: add machconfig
  tslib: enable big endian support for qemuppc

 meta/conf/machine/qemuppc.conf                     |    2 +-
 .../formfactor/files/qemuppc/machconfig            |   10 ++++++++++
 .../pointercal/files/qemuppc/pointercal            |  Bin 0 -> 36 bytes
 meta/recipes-graphics/tslib/tslib_1.0.bb           |    1 +
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.0.bb       |   15 ++++++++-------
 scripts/runqemu                                    |    7 +------
 scripts/runqemu-internal                           |   16 ++++++++--------
 8 files changed, 32 insertions(+), 25 deletions(-)
 create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
 create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal

-- 
1.7.4.1

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Saul Wold]

On 01/11/2012 10:52 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Since this is a stabilization week, this probably can't be merged
> immediately, but I've been working with this enough to call it
> good enough, and me sitting on them longer doesn't help.
>
> The first change in this series is the switch of qemuppc from prep to
> mac99. With this, we'll close a whole set of issues (slow bootup) and
> close a feature gap that has existed for a while.
>
> I'm seeing a bit of strangeness with the mouse in my sato testing,
> but that's about it. Liming hasn't seen the same issues, so getting
> this into the tree will allow us to incrementally improve and debug
> this.
>
> The second change is a SRCREV update pulls in the forward looking
> fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
> that was found on the routerstationpro.
>
> Cheers,
>
> Bruce
>
> cc: Khem Raj<raj.khem@gmail.com>
> cc: Zumeng Chen<zumeng.chen@windriver.com>
> cc: Liming Wang<liming.wang@windriver.com>
>
> The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
>
>    package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
>
> 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 (1):
>    linux-yocto: consolidated fix SRCREV updates
>
> Liming Wang (4):
>    qemuppc: replace emulation of qemuppc from prep to mac99
>    qemuppc: add pointercal file
>    qemuppc: add machconfig
>    tslib: enable big endian support for qemuppc
>
>   meta/conf/machine/qemuppc.conf                     |    2 +-
>   .../formfactor/files/qemuppc/machconfig            |   10 ++++++++++
>   .../pointercal/files/qemuppc/pointercal            |  Bin 0 ->  36 bytes
>   meta/recipes-graphics/tslib/tslib_1.0.bb           |    1 +
>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    6 +++---
>   meta/recipes-kernel/linux/linux-yocto_3.0.bb       |   15 ++++++++-------
>   scripts/runqemu                                    |    7 +------
>   scripts/runqemu-internal                           |   16 ++++++++--------
>   8 files changed, 32 insertions(+), 25 deletions(-)
>   create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
>   create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
>
Merged into OE-Core

Thanks
	Sau!

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Richard/Saul,

This is a follow on to the 3.2 tree and src_patches changes that I sent
last week.

The ability to specify out of tree BSPs via single .scc files is not 
possible, as well as any automatic BSPs following the naming conventions
of the 3.2 tree.

The meta branch changes are routine, with the exception being that I got
a report that 3.0 -rt wasn't patching. That report turned out to be true,
and I've fixed it here.

Cheers,

Bruce

The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:

  libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)

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 (5):
  linux-yocto: locate and use out of tree features specified on the
    SRC_URI
  linux-yocto: meta updates for sys940x and cleanup
  linux-yocto: rt compiliation fix
  kern-tools: remove explicit 'yocto' references from auto-bsp handling
  linux-yocto: fri2: use emgd-1.10

 meta/classes/kernel-yocto.bbclass                  |   21 ++++++++++++++++++++
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    2 +-
 meta/recipes-kernel/linux/linux-yocto_3.0.bb       |    2 +-
 meta/recipes-kernel/linux/linux-yocto_3.2.bb       |    2 +-
 5 files changed, 25 insertions(+), 4 deletions(-)

-- 
1.7.4.1

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Saul Wold]

On 02/04/2012 10:31 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> This is a follow on to the 3.2 tree and src_patches changes that I sent
> last week.
>
> The ability to specify out of tree BSPs via single .scc files is not
> possible, as well as any automatic BSPs following the naming conventions
> of the 3.2 tree.
>
> The meta branch changes are routine, with the exception being that I got
> a report that 3.0 -rt wasn't patching. That report turned out to be true,
> and I've fixed it here.
>
> Cheers,
>
> Bruce
>
> The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
>
>    libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
>
> 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 (5):
>    linux-yocto: locate and use out of tree features specified on the
>      SRC_URI
>    linux-yocto: meta updates for sys940x and cleanup
>    linux-yocto: rt compiliation fix
>    kern-tools: remove explicit 'yocto' references from auto-bsp handling
>    linux-yocto: fri2: use emgd-1.10
>
>   meta/classes/kernel-yocto.bbclass                  |   21 ++++++++++++++++++++
>   .../kern-tools/kern-tools-native_git.bb            |    2 +-
>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    2 +-
>   meta/recipes-kernel/linux/linux-yocto_3.0.bb       |    2 +-
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb       |    2 +-
>   5 files changed, 25 insertions(+), 4 deletions(-)
>

Merged into OE-core with updated patch set

Thanks
	Sau!

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Richard/Saul,

Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
mark on). I've built and booted core-image-sato for all the oe-core
qemu machines.

3.10 also the latest LTSI and will be updated with that content when it
becomes available.

Other features of the 3.10 kernel include:

  - refreshed -rt support
  - refreshed yaffs2, aufs3
  - cryptodev
  - bfs, edf, and OCF staged features
  - scrubbed and updated meta data for v3.10
  - improved tools support for meta data updates and queue maintenance
  - patch carry forward from all previous linux-yocto kernels and
    configuration.

I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.

I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
to adapt to a changed #define in the exported headers.

Other parts of this update include an uprev of guilt, and in fact, a 
restoration of "normal" guil operations, since the kernel tree is now
manipulated and maintained via a smaller, more contained script. This
was necessary for both usability reasons and the fact that all of guilts
protections were being removed for the kernel's use .. which makes you
ask the quesetion "why use it". It was time for a change.

The patches are pretty self explanitory and all contain detailed long
logs .. but the summary is:

   [PATCH 1/5] kern-tools: usability, bug fixes and no guilt  
   [PATCH 2/5] guilt: update to latest git version
   [PATCH 3/5] linux-libc-headers: update to v3.10
   [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
   [PATCH 5/5] linux-yocto: introduce v3.10

** There is one pending activity. As part of thsi update to 3.10, we want
to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the 
routerstationpro BSP is still using it as its preferred version. I'm
a one man show on this update, and I wasn't able to get the 100+ patches
ported to 3.10 AND get this update out before the M4 cutoff.

** I'm still attempting to udpate all the reference boards, and
once done, I'll send a follow up patch.

** Please test, I've done my best, but things can slip through. We'll
work issues in the stabilization period.

Cheers,

Bruce


The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:

  bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +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 (5):
  kern-tools: usability, bug fixes and no guilt
  guilt: update to latest git version
  linux-libc-headers: update to v3.10
  gst-plugins-good: fix 3.10 libc-headers build failure
  linux-yocto: introduce v3.10

 meta/classes/kernel-yocto.bbclass                  |    2 +
 meta/conf/distro/include/tcmode-default.inc        |    2 +-
 .../guilt/files/guilt-import-commit.patch          |   96 ------
 meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
 meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
 .../guilt/files/guilt-push-no-series.patch         |   29 --
 meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
 .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
 ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
 meta/recipes-devtools/guilt/files/guilt.patch      |  319 --------------------
 .../guilt/files/improve_auto_header_gen.patch      |   71 -----
 .../files/make_git_commands_conditional.patch      |   48 ---
 .../guilt/files/optional_head_check.patch          |   60 ----
 .../guilt/files/uninstall_force.patch              |   14 -
 .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
 .../kern-tools/kern-tools-native_git.bb            |    6 +-
 .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
 .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
 meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
 ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
 .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
 23 files changed, 150 insertions(+), 861 deletions(-)
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
 delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
 rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
 delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
 create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch

-- 
1.7.10.4

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On Fri, Aug 23, 2013 at 2:08 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
>   - refreshed -rt support
>   - refreshed yaffs2, aufs3
>   - cryptodev
>   - bfs, edf, and OCF staged features
>   - scrubbed and updated meta data for v3.10
>   - improved tools support for meta data updates and queue maintenance
>   - patch carry forward from all previous linux-yocto kernels and
>     configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
>    [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>    [PATCH 2/5] guilt: update to latest git version
>    [PATCH 3/5] linux-libc-headers: update to v3.10
>    [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>    [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.

Good news on this front. The routerstation pro (and it's replacement after
1.5) are working on 3.10 with the patches rebased. I'll follow up later with
the update of the rsp and the removal of the 3.8 recipe.

The beagleboard and fsl board will follow after that as well, pending some
boot testing.

Cheers,

Bruce

>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
>   bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +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 (5):
>   kern-tools: usability, bug fixes and no guilt
>   guilt: update to latest git version
>   linux-libc-headers: update to v3.10
>   gst-plugins-good: fix 3.10 libc-headers build failure
>   linux-yocto: introduce v3.10
>
>  meta/classes/kernel-yocto.bbclass                  |    2 +
>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>  .../guilt/files/guilt-import-commit.patch          |   96 ------
>  meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>  meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>  .../guilt/files/guilt-push-no-series.patch         |   29 --
>  meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>  .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>  ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>  meta/recipes-devtools/guilt/files/guilt.patch      |  319 --------------------
>  .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>  .../files/make_git_commands_conditional.patch      |   48 ---
>  .../guilt/files/optional_head_check.patch          |   60 ----
>  .../guilt/files/uninstall_force.patch              |   14 -
>  .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>  .../kern-tools/kern-tools-native_git.bb            |    6 +-
>  .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>  .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>  meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>  meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>  meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>  ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>  .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>  23 files changed, 150 insertions(+), 861 deletions(-)
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
>  delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
>  rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
>  create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>  delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>  create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Saul Wold]

On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
>    - refreshed -rt support
>    - refreshed yaffs2, aufs3
>    - cryptodev
>    - bfs, edf, and OCF staged features
>    - scrubbed and updated meta data for v3.10
>    - improved tools support for meta data updates and queue maintenance
>    - patch carry forward from all previous linux-yocto kernels and
>      configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>     [PATCH 2/5] guilt: update to latest git version
>     [PATCH 3/5] linux-libc-headers: update to v3.10
One of the changes in 3.10 seems to have introduced a conflicting 
definition of ptrace_peeksiginfo_args in linux/ptrace.h

>  In file included from ptrace.h:22:0,
> |                  from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args'
> |  struct ptrace_peeksiginfo_args {
> |         ^
> | In file included from ptrace.h:9:0,
> |                  from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8: note: originally defined here
> |  struct ptrace_peeksiginfo_args
> |         ^

This affects ltp, valgrind and strace.

Please check the autobuilder as I am building with this change set and 
expect these failures.

Sau!

Sau!

>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>     [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +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 (5):
>    kern-tools: usability, bug fixes and no guilt
>    guilt: update to latest git version
>    linux-libc-headers: update to v3.10
>    gst-plugins-good: fix 3.10 libc-headers build failure
>    linux-yocto: introduce v3.10
>
>   meta/classes/kernel-yocto.bbclass                  |    2 +
>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>   meta/recipes-devtools/guilt/files/guilt.patch      |  319 --------------------
>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>   .../files/make_git_commands_conditional.patch      |   48 ---
>   .../guilt/files/optional_head_check.patch          |   60 ----
>   .../guilt/files/uninstall_force.patch              |   14 -
>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>   23 files changed, 150 insertions(+), 861 deletions(-)
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
>   delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
>   create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>   delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>   create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 2:33 AM, Saul Wold wrote:
> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> Here's my consolidated set of changes that represent the biggest chunk
>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>> mark on). I've built and booted core-image-sato for all the oe-core
>> qemu machines.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>>    - refreshed -rt support
>>    - refreshed yaffs2, aufs3
>>    - cryptodev
>>    - bfs, edf, and OCF staged features
>>    - scrubbed and updated meta data for v3.10
>>    - improved tools support for meta data updates and queue maintenance
>>    - patch carry forward from all previous linux-yocto kernels and
>>      configuration.
>>
>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>> shiny tree.
>>
>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>> gst-plugins-good
>> to adapt to a changed #define in the exported headers.
>>
>> Other parts of this update include an uprev of guilt, and in fact, a
>> restoration of "normal" guil operations, since the kernel tree is now
>> manipulated and maintained via a smaller, more contained script. This
>> was necessary for both usability reasons and the fact that all of guilts
>> protections were being removed for the kernel's use .. which makes you
>> ask the quesetion "why use it". It was time for a change.
>>
>> The patches are pretty self explanitory and all contain detailed long
>> logs .. but the summary is:
>>
>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>     [PATCH 2/5] guilt: update to latest git version
>>     [PATCH 3/5] linux-libc-headers: update to v3.10
> One of the changes in 3.10 seems to have introduced a conflicting
> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>
>>  In file included from ptrace.h:22:0,
>> |                  from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>> |  struct ptrace_peeksiginfo_args {
>> |         ^
>> | In file included from ptrace.h:9:0,
>> |                  from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>> note: originally defined here
>> |  struct ptrace_peeksiginfo_args
>> |         ^
>
> This affects ltp, valgrind and strace.
>
> Please check the autobuilder as I am building with this change set and
> expect these failures.

I'm unfortunately off for the weekend and won't have cycles to look into
any failures until Monday.

So if you want to leave the old headers in place, that's an option.

I fixed the one issue that I saw with Sato .. but I am after all one
person and can't possibly build and boot all the qemu boards with
all image combinations! This is after all, where I'd expect other
people to help out and fix build issues.

Cheers,

Bruce

>
> Sau!
>
> Sau!
>
>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>
>> ** There is one pending activity. As part of thsi update to 3.10, we want
>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>> routerstationpro BSP is still using it as its preferred version. I'm
>> a one man show on this update, and I wasn't able to get the 100+ patches
>> ported to 3.10 AND get this update out before the M4 cutoff.
>>
>> ** I'm still attempting to udpate all the reference boards, and
>> once done, I'll send a follow up patch.
>>
>> ** Please test, I've done my best, but things can slip through. We'll
>> work issues in the stabilization period.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> The following changes since commit
>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>
>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +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 (5):
>>    kern-tools: usability, bug fixes and no guilt
>>    guilt: update to latest git version
>>    linux-libc-headers: update to v3.10
>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>    linux-yocto: introduce v3.10
>>
>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>> --------------------
>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>   .../guilt/files/uninstall_force.patch              |   14 -
>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>
>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>   delete mode 100644
>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>> guilt-native_git.bb} (45%)
>>   create mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>   delete mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>   create mode 100644
>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>
>>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 9:34 AM, Bruce Ashfield wrote:
> On 13-08-24 2:33 AM, Saul Wold wrote:
>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>> Richard/Saul,
>>>
>>> Here's my consolidated set of changes that represent the biggest chunk
>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>> mark on). I've built and booted core-image-sato for all the oe-core
>>> qemu machines.
>>>
>>> 3.10 also the latest LTSI and will be updated with that content when it
>>> becomes available.
>>>
>>> Other features of the 3.10 kernel include:
>>>
>>>    - refreshed -rt support
>>>    - refreshed yaffs2, aufs3
>>>    - cryptodev
>>>    - bfs, edf, and OCF staged features
>>>    - scrubbed and updated meta data for v3.10
>>>    - improved tools support for meta data updates and queue maintenance
>>>    - patch carry forward from all previous linux-yocto kernels and
>>>      configuration.
>>>
>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>> shiny tree.
>>>
>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>> gst-plugins-good
>>> to adapt to a changed #define in the exported headers.
>>>
>>> Other parts of this update include an uprev of guilt, and in fact, a
>>> restoration of "normal" guil operations, since the kernel tree is now
>>> manipulated and maintained via a smaller, more contained script. This
>>> was necessary for both usability reasons and the fact that all of guilts
>>> protections were being removed for the kernel's use .. which makes you
>>> ask the quesetion "why use it". It was time for a change.
>>>
>>> The patches are pretty self explanitory and all contain detailed long
>>> logs .. but the summary is:
>>>
>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>     [PATCH 2/5] guilt: update to latest git version
>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>> One of the changes in 3.10 seems to have introduced a conflicting
>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>
>>>  In file included from ptrace.h:22:0,
>>> |                  from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>
>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>> |  struct ptrace_peeksiginfo_args {
>>> |         ^
>>> | In file included from ptrace.h:9:0,
>>> |                  from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>
>>> note: originally defined here
>>> |  struct ptrace_peeksiginfo_args
>>> |         ^
>>
>> This affects ltp, valgrind and strace.
>>
>> Please check the autobuilder as I am building with this change set and
>> expect these failures.
>
> I'm unfortunately off for the weekend and won't have cycles to look into
> any failures until Monday.

As it turns out, I may have some time to work on this tonight, since I
have to delete the 3.8 yocto recipe and get that patch out.

So I've launched a LSB build in the background and will check on it
later.

If anyone else does get a fix for this, make sure to cc' me on any
changes, so I won't spend time trying to fix it a second time! :)

Bruce

>
> So if you want to leave the old headers in place, that's an option.
>
> I fixed the one issue that I saw with Sato .. but I am after all one
> person and can't possibly build and boot all the qemu boards with
> all image combinations! This is after all, where I'd expect other
> people to help out and fix build issues.
>
> Cheers,
>
> Bruce
>
>>
>> Sau!
>>
>> Sau!
>>
>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>
>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>> want
>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>> routerstationpro BSP is still using it as its preferred version. I'm
>>> a one man show on this update, and I wasn't able to get the 100+ patches
>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>
>>> ** I'm still attempting to udpate all the reference boards, and
>>> once done, I'll send a follow up patch.
>>>
>>> ** Please test, I've done my best, but things can slip through. We'll
>>> work issues in the stabilization period.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>> The following changes since commit
>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>
>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>> +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 (5):
>>>    kern-tools: usability, bug fixes and no guilt
>>>    guilt: update to latest git version
>>>    linux-libc-headers: update to v3.10
>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>    linux-yocto: introduce v3.10
>>>
>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>> --------------------
>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>
>>>
>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>   delete mode 100644
>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>> guilt-native_git.bb} (45%)
>>>   create mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>   delete mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>   create mode 100644
>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>
>>>
>>>
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Saul Wold]

On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>> Richard/Saul,
>>>>
>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>> qemu machines.
>>>>
>>>> 3.10 also the latest LTSI and will be updated with that content when it
>>>> becomes available.
>>>>
>>>> Other features of the 3.10 kernel include:
>>>>
>>>>    - refreshed -rt support
>>>>    - refreshed yaffs2, aufs3
>>>>    - cryptodev
>>>>    - bfs, edf, and OCF staged features
>>>>    - scrubbed and updated meta data for v3.10
>>>>    - improved tools support for meta data updates and queue maintenance
>>>>    - patch carry forward from all previous linux-yocto kernels and
>>>>      configuration.
>>>>
>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>> shiny tree.
>>>>
>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>> gst-plugins-good
>>>> to adapt to a changed #define in the exported headers.
>>>>
>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>> manipulated and maintained via a smaller, more contained script. This
>>>> was necessary for both usability reasons and the fact that all of
>>>> guilts
>>>> protections were being removed for the kernel's use .. which makes you
>>>> ask the quesetion "why use it". It was time for a change.
>>>>
>>>> The patches are pretty self explanitory and all contain detailed long
>>>> logs .. but the summary is:
>>>>
>>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>     [PATCH 2/5] guilt: update to latest git version
>>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>>> One of the changes in 3.10 seems to have introduced a conflicting
>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>
>>>>  In file included from ptrace.h:22:0,
>>>> |                  from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>
>>>>
>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>> |  struct ptrace_peeksiginfo_args {
>>>> |         ^
>>>> | In file included from ptrace.h:9:0,
>>>> |                  from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>
>>>>
>>>> note: originally defined here
>>>> |  struct ptrace_peeksiginfo_args
>>>> |         ^
>>>
>>> This affects ltp, valgrind and strace.
>>>
>>> Please check the autobuilder as I am building with this change set and
>>> expect these failures.
>>
>> I'm unfortunately off for the weekend and won't have cycles to look into
>> any failures until Monday.
>
> As it turns out, I may have some time to work on this tonight, since I
> have to delete the 3.8 yocto recipe and get that patch out.
>
> So I've launched a LSB build in the background and will check on it
> later.
>
Just FYI, it might not show up in an LSB build, since those tools 
valgrind, ltp and strace are more Dev tools, so a world build would be 
better.

Also, not sure why but ARM failed to patch 3.8 kernel overnight on the 
AB. (lots of red).

I just restarted AB with out the 3.10 headers.

Sau!

> If anyone else does get a fix for this, make sure to cc' me on any
> changes, so I won't spend time trying to fix it a second time! :)
>
> Bruce
>
>>
>> So if you want to leave the old headers in place, that's an option.
>>
>> I fixed the one issue that I saw with Sato .. but I am after all one
>> person and can't possibly build and boot all the qemu boards with
>> all image combinations! This is after all, where I'd expect other
>> people to help out and fix build issues.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> Sau!
>>>
>>> Sau!
>>>
>>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>>
>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>> want
>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>> a one man show on this update, and I wasn't able to get the 100+
>>>> patches
>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>
>>>> ** I'm still attempting to udpate all the reference boards, and
>>>> once done, I'll send a follow up patch.
>>>>
>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>> work issues in the stabilization period.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>
>>>> The following changes since commit
>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>
>>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>> +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 (5):
>>>>    kern-tools: usability, bug fixes and no guilt
>>>>    guilt: update to latest git version
>>>>    linux-libc-headers: update to v3.10
>>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>>    linux-yocto: introduce v3.10
>>>>
>>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>>> --------------------
>>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>
>>>>
>>>>
>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>   delete mode 100644
>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>> guilt-native_git.bb} (45%)
>>>>   create mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>   delete mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>   create mode 100644
>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>
>>>>
>>>>
>>>>
>>
>
>
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>>    - refreshed -rt support
>>>>>    - refreshed yaffs2, aufs3
>>>>>    - cryptodev
>>>>>    - bfs, edf, and OCF staged features
>>>>>    - scrubbed and updated meta data for v3.10
>>>>>    - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>>    - patch carry forward from all previous linux-yocto kernels and
>>>>>      configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>>     [PATCH 2/5] guilt: update to latest git version
>>>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>>  In file included from ptrace.h:22:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> |  struct ptrace_peeksiginfo_args {
>>>>> |         ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> |  struct ptrace_peeksiginfo_args
>>>>> |         ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.

Ah ok. I'll explicitly add dependencies on them here and restart
my sato build.

I'm a bit surprised that it failed, since user apis are a huge no-no
to change.

>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).

probably because I didn't look at 3.8 ... since my plan was to delete
it!

I'll follow up with a fix for that tonight, if I can see the failure
here. Always fun!! :)

Leave that one with me. Do you have a link to the failure ?

Bruce

>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +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 (5):
>>>>>    kern-tools: usability, bug fixes and no guilt
>>>>>    guilt: update to latest git version
>>>>>    linux-libc-headers: update to v3.10
>>>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>    linux-yocto: introduce v3.10
>>>>>
>>>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>>>> --------------------
>>>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>>   delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>>    - refreshed -rt support
>>>>>    - refreshed yaffs2, aufs3
>>>>>    - cryptodev
>>>>>    - bfs, edf, and OCF staged features
>>>>>    - scrubbed and updated meta data for v3.10
>>>>>    - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>>    - patch carry forward from all previous linux-yocto kernels and
>>>>>      configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>>     [PATCH 2/5] guilt: update to latest git version
>>>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>>  In file included from ptrace.h:22:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> |  struct ptrace_peeksiginfo_args {
>>>>> |         ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> |  struct ptrace_peeksiginfo_args
>>>>> |         ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.

I reproduced the failure here via adding ptrace to my image install.
The kernel change happened in april, and the good news is that the
structure is still exactly the same size, with the same fields. So the
userspace ABI is unchanged.

I'll hunt down the conflict and adjust the packages, since that kernel
header change will be there to stay.

Has anyone checked to see if the upstream version of those packages have
already adapted to the change ? I'll do that tonight when I'm back, if
no one else has.

Cheers,

Bruce

>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +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 (5):
>>>>>    kern-tools: usability, bug fixes and no guilt
>>>>>    guilt: update to latest git version
>>>>>    linux-libc-headers: update to v3.10
>>>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>    linux-yocto: introduce v3.10
>>>>>
>>>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>>>> --------------------
>>>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>>   delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>>    - refreshed -rt support
>>>>>    - refreshed yaffs2, aufs3
>>>>>    - cryptodev
>>>>>    - bfs, edf, and OCF staged features
>>>>>    - scrubbed and updated meta data for v3.10
>>>>>    - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>>    - patch carry forward from all previous linux-yocto kernels and
>>>>>      configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>>     [PATCH 2/5] guilt: update to latest git version
>>>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>>  In file included from ptrace.h:22:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> |  struct ptrace_peeksiginfo_args {
>>>>> |         ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> |  struct ptrace_peeksiginfo_args
>>>>> |         ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.

ok .. this time I'm REALLY going to step away for a few hours.

The mismatch is between the eglibc 2.18 sys/ptrace.h and the kernel's
definition of the structure. I wouldn't really call it a mismatch,
since they are both the same size and field types .. both simply
define it now.

I'm adding Khem: What's the right thing to do here?

I can obviously hack the kernel to remove the definition, but that make
the linux-yocto 3.10 the only kernel that will work against yocto 1.5's
eglibc for building any applications that use ptrace.h.

Falling back to the 3.8 headers will work, but again, we are avoiding
the problem and any end user that does bump to a newer set of libc-headers
will see the problem.

I'll wait for consensus on the approach and add a change if required
into my linux-yocto 3.8 removal patch tonight.

Bruce

>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +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 (5):
>>>>>    kern-tools: usability, bug fixes and no guilt
>>>>>    guilt: update to latest git version
>>>>>    linux-libc-headers: update to v3.10
>>>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>    linux-yocto: introduce v3.10
>>>>>
>>>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>>>> --------------------
>>>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>>   delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>>    - refreshed -rt support
>>>>>    - refreshed yaffs2, aufs3
>>>>>    - cryptodev
>>>>>    - bfs, edf, and OCF staged features
>>>>>    - scrubbed and updated meta data for v3.10
>>>>>    - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>>    - patch carry forward from all previous linux-yocto kernels and
>>>>>      configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>>     [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>>     [PATCH 2/5] guilt: update to latest git version
>>>>>     [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>>  In file included from ptrace.h:22:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> |  struct ptrace_peeksiginfo_args {
>>>>> |         ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> |                  from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> |  struct ptrace_peeksiginfo_args
>>>>> |         ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).

FYI: I've fixed the ARM 3.8 build issue here, it'll be in my series
tonight .. regardless if I'm removing 3.8, it was worth fixing.

Cheers,

Bruce

>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>>     [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>     [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>>    bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +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 (5):
>>>>>    kern-tools: usability, bug fixes and no guilt
>>>>>    guilt: update to latest git version
>>>>>    linux-libc-headers: update to v3.10
>>>>>    gst-plugins-good: fix 3.10 libc-headers build failure
>>>>>    linux-yocto: introduce v3.10
>>>>>
>>>>>   meta/classes/kernel-yocto.bbclass                  |    2 +
>>>>>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>>   .../guilt/files/guilt-import-commit.patch          |   96 ------
>>>>>   meta/recipes-devtools/guilt/files/guilt-init.patch |   25 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-pop.patch  |   73 -----
>>>>>   .../guilt/files/guilt-push-no-series.patch         |   29 --
>>>>>   meta/recipes-devtools/guilt/files/guilt-push.patch |   42 ---
>>>>>   .../guilt/files/guilt-set-git_exec_path.patch      |   29 --
>>>>>   ...lt-update-supported-git-versions-to-1.8.x.patch |   28 --
>>>>>   meta/recipes-devtools/guilt/files/guilt.patch      |  319
>>>>> --------------------
>>>>>   .../guilt/files/improve_auto_header_gen.patch      |   71 -----
>>>>>   .../files/make_git_commands_conditional.patch      |   48 ---
>>>>>   .../guilt/files/optional_head_check.patch          |   60 ----
>>>>>   .../guilt/files/uninstall_force.patch              |   14 -
>>>>>   .../{guilt-native_0.33.bb => guilt-native_git.bb}  |   21 +-
>>>>>   .../kern-tools/kern-tools-native_git.bb            |    6 +-
>>>>>   .../linux-libc-headers/linux-libc-headers_3.10.bb  |    7 +
>>>>>   .../linux-libc-headers/linux-libc-headers_3.8.bb   |    8 -
>>>>>   meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |   30 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |   25 ++
>>>>>   meta/recipes-kernel/linux/linux-yocto_3.10.bb      |   30 ++
>>>>>   ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch |   45 +++
>>>>>   .../gstreamer/gst-plugins-good_0.10.31.bb          |    1 +
>>>>>   23 files changed, 150 insertions(+), 861 deletions(-)
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>>   delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>>   rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>>   delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>>   create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of
kernel version -stable imports (CVEs and fixes), kernel configuration 
changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here
(with my fixup commits being evidence). These are ready for a round of
autobuilder/soak testing.

The only other change is the addition of the ability to use a defconfig
that is maintained within a kernel tree. This enhacement request came
from the raspberrypi2 maintainers. We went through a few revisions and
test cycles on this (see YOCTO: 7474 for the details). 

The final result has no impact on existing configuration workflows, but
does allow an in-tree config to be copied out into WORKDIR and then
incorporated with other fragments as part of kconfig processing. A new
variable is introduced for specifying the defconfig KBUILD_DEFCONFIG,
and I'll work with Scott to make sure this is documented in the 
appropriate locations.

Cheers,

Bruce


The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:

  yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +0000)

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 (5):
  kernel-yocto: allow in-tree defconfigs
  linux-yocto/3.19: configuration updates and stable import
  linux-yocto/3.14: integrate korg stable and meta data changes
  linux-yocto/3.19: fixes for Intel core warnings
  skeleton: clarify linux-yocto-custom workflow

 .../recipes-kernel/linux/linux-yocto-custom.bb     |  6 ++--
 meta/classes/kernel-yocto.bbclass                  | 39 ++++++++++++++++++++--
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  8 ++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 20 +++++------
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 20 +++++------
 7 files changed, 69 insertions(+), 36 deletions(-)

-- 
2.1.0

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> Hi all,
> 
> Here is the latest linux-yocto consolidated pull request. It is a mix of
> kernel version -stable imports (CVEs and fixes), kernel configuration 
> changes, a documentation update and kernel configuration enhancement.
> 
> The -stable updates are routine, and I build/boot tested them here
> (with my fixup commits being evidence). These are ready for a round of
> autobuilder/soak testing.

Something in here broke lttng-modules causing cascades of failures on
the autobuilder so I've updated it to the latest code on the 2.6 stable
branch and am retesting.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>> Hi all,
>>
>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>> kernel version -stable imports (CVEs and fixes), kernel configuration
>> changes, a documentation update and kernel configuration enhancement.
>>
>> The -stable updates are routine, and I build/boot tested them here
>> (with my fixup commits being evidence). These are ready for a round of
>> autobuilder/soak testing.
>
> Something in here broke lttng-modules causing cascades of failures on
> the autobuilder so I've updated it to the latest code on the 2.6 stable
> branch and am retesting.

Gah. I built and booted here, but can't think of any reason why that didn't
trigger and fail here.

I've started my own build as well, with a completely clean starting point.

Bruce

>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>>> Hi all,
>>>
>>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>>> kernel version -stable imports (CVEs and fixes), kernel configuration
>>> changes, a documentation update and kernel configuration enhancement.
>>>
>>> The -stable updates are routine, and I build/boot tested them here
>>> (with my fixup commits being evidence). These are ready for a round of
>>> autobuilder/soak testing.
>>
>> Something in here broke lttng-modules causing cascades of failures on
>> the autobuilder so I've updated it to the latest code on the 2.6 stable
>> branch and am retesting.
>
> Gah. I built and booted here, but can't think of any reason why that didn't
> trigger and fail here.
>
> I've started my own build as well, with a completely clean starting point.

and sure enough, it blows up on my clean build.

If your update doesn't resolve this, ping me and I'll take care of the fix.

Bruce

>
> Bruce
>
>>
>> Cheers,
>>
>> Richard
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Wed, 2015-03-25 at 09:26 -0400, Bruce Ashfield wrote:
> On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> >>> Hi all,
> >>>
> >>> Here is the latest linux-yocto consolidated pull request. It is a mix of
> >>> kernel version -stable imports (CVEs and fixes), kernel configuration
> >>> changes, a documentation update and kernel configuration enhancement.
> >>>
> >>> The -stable updates are routine, and I build/boot tested them here
> >>> (with my fixup commits being evidence). These are ready for a round of
> >>> autobuilder/soak testing.
> >>
> >> Something in here broke lttng-modules causing cascades of failures on
> >> the autobuilder so I've updated it to the latest code on the 2.6 stable
> >> branch and am retesting.
> >
> > Gah. I built and booted here, but can't think of any reason why that didn't
> > trigger and fail here.
> >
> > I've started my own build as well, with a completely clean starting point.
> 
> and sure enough, it blows up on my clean build.
> 
> If your update doesn't resolve this, ping me and I'll take care of the fix.

It seemed to work, we've merged everything to master and branched for
the release. Release build now in progress so we'll see... :)

Cheers,

Richard

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Here is the latest consolidated pull request for the supported linux-yocto
kernels.

 - We have a refresh of the 3.14-rt support
 - bluetooh configuration changes for common-pc/qemux86
 - braswell BSP features and fixes
 - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).

I've built and booted these on my local machines and qemu, and
everything was sane.

The -dev kernel obviously isn't something for deployment yet, but
it builds, and forms the base for follow up config changes, features
and development work. I built and booted core-image-kernel dev with
the 4.1 changes in place.

Cheers,

Bruce

The following changes since commit db409697db2ea0931cdcd2015d089b6b0ea39bbb:

  bitbake: bitbake: reset build mtime cache before the build (2015-04-29 10:59:54 +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 (5):
  linux-yocto/3.14: refresh -rt support
  linux-yocto: add core bluetooth support to qemux86* and common-pc*
  linux-yocto/3.19: Braswell support and bug fixes
  perf: fix build (and feature tests) for 4.1-rcX
  linux-yocto-dev: introduce 4.1-rc development kernel

 meta/recipes-kernel/linux/linux-yocto-dev.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 18 +++++++++---------
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 18 +++++++++---------
 meta/recipes-kernel/perf/perf.bb                   |  3 +++
 7 files changed, 29 insertions(+), 26 deletions(-)

-- 
2.1.0

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
> 
>  - We have a refresh of the 3.14-rt support
>  - bluetooh configuration changes for common-pc/qemux86
>  - braswell BSP features and fixes
>  - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> 
> I've built and booted these on my local machines and qemu, and
> everything was sane.
> 
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.

The autobuilder showed up this for an x32 build :/.

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-01 6:59 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>>   - We have a refresh of the 3.14-rt support
>>   - bluetooh configuration changes for common-pc/qemux86
>>   - braswell BSP features and fixes
>>   - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> The autobuilder showed up this for an x32 build :/.

Can one of the intel folks have a look at this ? I won't be able to get
to it until Tuesday at the earliest.

Bruce

>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>
> Cheers,
>
> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Martin Jansa]

On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >>   - We have a refresh of the 3.14-rt support
> >>   - bluetooh configuration changes for common-pc/qemux86
> >>   - braswell BSP features and fixes
> >>   - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.

Does it fix the issue I've reported few days ago?
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html

> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
> 
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
> 
> Bruce
> 
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >
> > Cheers,
> >
> > Richard
> >
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >>   - We have a refresh of the 3.14-rt support
> >>   - bluetooh configuration changes for common-pc/qemux86
> >>   - braswell BSP features and fixes
> >>   - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
> >>
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
> 
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.

I had a look into this. The issue is that this has been applied:

http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69

but it needs:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86

and the ioapic driver also appears to need:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e


which meant I also had to add:

struct resource_win {
	struct resource res;		/* In master (CPU) address space */
	resource_size_t offset;		/* Translation offset for bridge */
};

to drivers/acpi/ioapic.c to make it compile which appears to be related to:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863

which depends on a number of patches from around that time which change acpi/resource.c:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c

(from 2015/2/3)

At this point I'm out my depth on how you want to fix this but it does
appear related to the Braswell changes.

To be clear qemux86 and qemux86-64 don't build at all with this series.
I'll see if I can just drop the Braswell parts.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-02 4:13 AM, Martin Jansa wrote:
> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>>    - We have a refresh of the 3.14-rt support
>>>>    - bluetooh configuration changes for common-pc/qemux86
>>>>    - braswell BSP features and fixes
>>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>
> Does it fix the issue I've reported few days ago?
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html

Nope. But one config warning is far down on the list when I'm
trying to introduce new -stable's and an entire -dev kernel.

I didn't forget about it, it'll just get done in priority order.

Bruce

>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>>
>> Bruce
>>
>>>
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>>    - We have a refresh of the 3.14-rt support
>>>>    - bluetooh configuration changes for common-pc/qemux86
>>>>    - braswell BSP features and fixes
>>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> 	struct resource res;		/* In master (CPU) address space */
> 	resource_size_t offset;		/* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.

Gah. It figures. That's of course the issue with any set of BSP ports ..
they get tangled up with Greg's series from time to time.

The changes are all additive, so we can't really drop the braswell parts
unless I revert the whole block of changes.

Drop those -stable updates for now, and I'll see if I can carve out some
time tomorrow to get that config building.

Bruce

>
> Cheers,
>
> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>>    - We have a refresh of the 3.14-rt support
>>>>    - bluetooh configuration changes for common-pc/qemux86
>>>>    - braswell BSP features and fixes
>>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> 	struct resource res;		/* In master (CPU) address space */
> 	resource_size_t offset;		/* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.

I did reproduce the issue here as well, so with any luck, I can sneak
enough time to have this fixed for Monday after all.

Bruce

>
> Cheers,
>
> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Sat, 2015-05-02 at 23:52 -0400, Bruce Ashfield wrote:
> On 2015-05-02 5:00 AM, Richard Purdie wrote:
> > On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>>    - We have a refresh of the 3.14-rt support
> >>>>    - bluetooh configuration changes for common-pc/qemux86
> >>>>    - braswell BSP features and fixes
> >>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >>>>
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >
> > I had a look into this. The issue is that this has been applied:
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
> >
> > but it needs:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
> >
> > and the ioapic driver also appears to need:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
> >
> >
> > which meant I also had to add:
> >
> > struct resource_win {
> > 	struct resource res;		/* In master (CPU) address space */
> > 	resource_size_t offset;		/* Translation offset for bridge */
> > };
> >
> > to drivers/acpi/ioapic.c to make it compile which appears to be related to:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
> >
> > which depends on a number of patches from around that time which change acpi/resource.c:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
> >
> > (from 2015/2/3)
> >
> > At this point I'm out my depth on how you want to fix this but it does
> > appear related to the Braswell changes.
> >
> > To be clear qemux86 and qemux86-64 don't build at all with this series.
> > I'll see if I can just drop the Braswell parts.
> 
> I did reproduce the issue here as well, so with any luck, I can sneak
> enough time to have this fixed for Monday after all.

From my perspective there isn't a rush at this point. I've merged the
config changes which unblocked the bluez patches and things are
therefore "flowing" from my perspective, the stable update can wait
until later in the week.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
> 
>  - We have a refresh of the 3.14-rt support
>  - bluetooh configuration changes for common-pc/qemux86
>  - braswell BSP features and fixes
>  - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> 
> I've built and booted these on my local machines and qemu, and
> everything was sane.
> 
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.

There was also a problem with poky-lsb. The idea (as far as I remember)
is that it should be using LTSI rather than the default main kernel so
we could split the testing. Unfortunately it was pointing at 3.10 which
doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
updated the PREFERRED_VERSION to that.

This resulted in this failure on the autobuilder:

https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio

Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
I've mixed the versions up, let me know which one poky-lsb should be
using.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-03 5:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>>   - We have a refresh of the 3.14-rt support
>>   - bluetooh configuration changes for common-pc/qemux86
>>   - braswell BSP features and fixes
>>   - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.

Correct on all counts. We did want it to use LTSI, and that is 3.14
at the moment.

>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If

Doesn't look to bad. I'll address this one along with the x32 build
failure on Monday (assuming I get it fixed in the day).

Bruce

> I've mixed the versions up, let me know which one poky-lsb should be
> using.
>
> Cheers,
>
> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-03 05:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>>   - We have a refresh of the 3.14-rt support
>>   - bluetooh configuration changes for common-pc/qemux86
>>   - braswell BSP features and fixes
>>   - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
> I've mixed the versions up, let me know which one poky-lsb should be

FYI: I've fixed the mips build. Looking at x86 now. SRCREV updates
to follow ASAP.

Bruce

> using.
>
> Cheers,
>
> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Martin Jansa]

On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> > On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>>    - We have a refresh of the 3.14-rt support
> >>>>    - bluetooh configuration changes for common-pc/qemux86
> >>>>    - braswell BSP features and fixes
> >>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >
> > Does it fix the issue I've reported few days ago?
> > http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> 
> Nope. But one config warning is far down on the list when I'm
> trying to introduce new -stable's and an entire -dev kernel.
> 
> I didn't forget about it, it'll just get done in priority order.

OK, now it fails completely in default qemux86 builds:

ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| NOTE: kernel configme
| [INFO] Configuring target/machine combo: "standard/qemux86"
| [INFO] collecting configs in .meta/meta-series
| [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
| Error running the meta series for collecting config data
| config of "standard/qemux86" failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'

http://errors.yoctoproject.org/Errors/Details/10481/

> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >>
> >> Bruce
> >>
> >>>
> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>
> >>> Cheers,
> >>>
> >>> Richard
> >>>
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-06 10:42 AM, Martin Jansa wrote:
> On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
>> On 2015-05-02 4:13 AM, Martin Jansa wrote:
>>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>>>> kernels.
>>>>>>
>>>>>>     - We have a refresh of the 3.14-rt support
>>>>>>     - bluetooh configuration changes for common-pc/qemux86
>>>>>>     - braswell BSP features and fixes
>>>>>>     - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>>> I've built and booted these on my local machines and qemu, and
>>>>>> everything was sane.
>>>
>>> Does it fix the issue I've reported few days ago?
>>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>>
>> Nope. But one config warning is far down on the list when I'm
>> trying to introduce new -stable's and an entire -dev kernel.
>>
>> I didn't forget about it, it'll just get done in priority order.
>
> OK, now it fails completely in default qemux86 builds:
>

At this point, all I can say is file a bug. My builds of the same
board work, and the autobuilder show up green.

That screams race condition, so I'll look into it from that angle.

Bruce

> ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> Log data follows:
> | DEBUG: Executing shell function do_kernel_configme
> | NOTE: kernel configme
> | [INFO] Configuring target/machine combo: "standard/qemux86"
> | [INFO] collecting configs in .meta/meta-series
> | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> | Error running the meta series for collecting config data
> | config of "standard/qemux86" failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
>
> http://errors.yoctoproject.org/Errors/Details/10481/
>
>>>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>>>> it builds, and forms the base for follow up config changes, features
>>>>>> and development work. I built and booted core-image-kernel dev with
>>>>>> the 4.1 changes in place.
>>>>>
>>>>> The autobuilder showed up this for an x32 build :/.
>>>>
>>>> Can one of the intel folks have a look at this ? I won't be able to get
>>>> to it until Tuesday at the earliest.
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Martin Jansa]

On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> >>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>>>> kernels.
> >>>>>>
> >>>>>>     - We have a refresh of the 3.14-rt support
> >>>>>>     - bluetooh configuration changes for common-pc/qemux86
> >>>>>>     - braswell BSP features and fixes
> >>>>>>     - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>>> I've built and booted these on my local machines and qemu, and
> >>>>>> everything was sane.
> >>>
> >>> Does it fix the issue I've reported few days ago?
> >>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >>
> >> Nope. But one config warning is far down on the list when I'm
> >> trying to introduce new -stable's and an entire -dev kernel.
> >>
> >> I didn't forget about it, it'll just get done in priority order.
> >
> > OK, now it fails completely in default qemux86 builds:
> >
> 
> At this point, all I can say is file a bug. My builds of the same
> board work, and the autobuilder show up green.
> 
> That screams race condition, so I'll look into it from that angle.

I'm considering providing simple old-style recipes for vanilla kernels
and using them in my jenkins builds instead linux-yocto, because kernel
shouldn't block testing other recipes from meta-oe and other layers as
often as linux-yocto does.

> > ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_configme
> > | NOTE: kernel configme
> > | [INFO] Configuring target/machine combo: "standard/qemux86"
> > | [INFO] collecting configs in .meta/meta-series
> > | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> > | Error running the meta series for collecting config data
> > | config of "standard/qemux86" failed
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> > ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
> >
> > http://errors.yoctoproject.org/Errors/Details/10481/
> >
> >>>>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>>>> it builds, and forms the base for follow up config changes, features
> >>>>>> and development work. I built and booted core-image-kernel dev with
> >>>>>> the 4.1 changes in place.
> >>>>>
> >>>>> The autobuilder showed up this for an x32 build :/.
> >>>>
> >>>> Can one of the intel folks have a look at this ? I won't be able to get
> >>>> to it until Tuesday at the earliest.
> >>>>
> >>>> Bruce
> >>>>
> >>>>>
> >>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Richard
> >>>>>
> >>>>
> >>>> --
> >>>> _______________________________________________
> >>>> Openembedded-core mailing list
> >>>> Openembedded-core@lists.openembedded.org
> >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >>>
> >>
> >
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > At this point, all I can say is file a bug. My builds of the same
> > board work, and the autobuilder show up green.
> > 
> > That screams race condition, so I'll look into it from that angle.
> 
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.

I wasn't aware of linux-yocto breaking that often?

I am aware that:

* we have a race issue with shared_work which we're trying to resolve
  and its proving tricky to find a patch which doesn't break builds

* we have the newly reported issue in this thread. FWIW the builders 
  I've seen are all green

* there are some warnings in the build which need addressing

but on the most part I thought we'd caught the serious kernel failures
in advance of changes hitting master. Are you using master-next or
master? 

Its its -next, I can understand the problems more as that has been
unstable recently but then by its nature, it can be. We are rooting out
problems before master afaict though?

Cheers,

Richard
 

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Martin Jansa]

On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> > On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > > At this point, all I can say is file a bug. My builds of the same
> > > board work, and the autobuilder show up green.
> > > 
> > > That screams race condition, so I'll look into it from that angle.
> > 
> > I'm considering providing simple old-style recipes for vanilla kernels
> > and using them in my jenkins builds instead linux-yocto, because kernel
> > shouldn't block testing other recipes from meta-oe and other layers as
> > often as linux-yocto does.
> 
> I wasn't aware of linux-yocto breaking that often?

Someone can query http://errors.yoctoproject.org/ database to see how
often (or if it's just me and my builds), unfortunately the full-text
search for "linux-yocto" doesn't provide good overview of issues,
because it shows 350 errors and not all are from linux-yocto recipe.

http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
on e-mail also aren't very accurate because I submit only reports from
relatively success full builds (so I usually skip the builds with failed
kernel, unless it's failing like that for long time).

> I am aware that:
> 
> * we have a race issue with shared_work which we're trying to resolve
>   and its proving tricky to find a patch which doesn't break builds
> 
> * we have the newly reported issue in this thread. FWIW the builders 
>   I've seen are all green
> 
> * there are some warnings in the build which need addressing
> 
> but on the most part I thought we'd caught the serious kernel failures
> in advance of changes hitting master. Are you using master-next or
> master? 

I've used master-next week or two ago (mostly to test bluez4 and python3
changes) and soon after that dropped all linux-yocto related changes
from it assuming that it's indeed cause for the issues I'm seeing, but
it's not and it's still failing with master as well (and my
jenkins/world builds are just small portion of my builds executed
elsewhere where I see similar issues).

> Its its -next, I can understand the problems more as that has been
> unstable recently but then by its nature, it can be. We are rooting out
> problems before master afaict though?
> 
> Cheers,
> 
> Richard

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-06 12:07 PM, Martin Jansa wrote:
> On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
>> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
>>> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-06 10:42 AM, Martin Jansa wrote:
>>>> At this point, all I can say is file a bug. My builds of the same
>>>> board work, and the autobuilder show up green.
>>>>
>>>> That screams race condition, so I'll look into it from that angle.
>>>
>>> I'm considering providing simple old-style recipes for vanilla kernels
>>> and using them in my jenkins builds instead linux-yocto, because kernel
>>> shouldn't block testing other recipes from meta-oe and other layers as
>>> often as linux-yocto does.
>>
>> I wasn't aware of linux-yocto breaking that often?
>
> Someone can query http://errors.yoctoproject.org/ database to see how
> often (or if it's just me and my builds), unfortunately the full-text
> search for "linux-yocto" doesn't provide good overview of issues,
> because it shows 350 errors and not all are from linux-yocto recipe.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
> on e-mail also aren't very accurate because I submit only reports from
> relatively success full builds (so I usually skip the builds with failed
> kernel, unless it's failing like that for long time).
>
>> I am aware that:
>>
>> * we have a race issue with shared_work which we're trying to resolve
>>    and its proving tricky to find a patch which doesn't break builds
>>
>> * we have the newly reported issue in this thread. FWIW the builders
>>    I've seen are all green
>>
>> * there are some warnings in the build which need addressing
>>
>> but on the most part I thought we'd caught the serious kernel failures
>> in advance of changes hitting master. Are you using master-next or
>> master?
>
> I've used master-next week or two ago (mostly to test bluez4 and python3
> changes) and soon after that dropped all linux-yocto related changes
> from it assuming that it's indeed cause for the issues I'm seeing, but
> it's not and it's still failing with master as well (and my
> jenkins/world builds are just small portion of my builds executed
> elsewhere where I see similar issues).

Richard: How can we sort out the differences between the build
environment that Martin uses versus what the autobuilder is showing?

There's nothing particularly complex happening during that build,
it's a checkout and generation of a config.

I'm unable to reproduce any of the failures, and neither is the
autobuilder.

I've stared at the code and can't see what could cause any of this.

That being said, I think I have a solution to what Martin is reporting
here, where I've changed the way the meta data is maintained and
build.

It will be ready in a week or so, so I'd be interested in us holding
on anything drastic until we can try that out.

Bruce

>
>> Its its -next, I can understand the problems more as that has been
>> unstable recently but then by its nature, it can be. We are rooting out
>> problems before master afaict though?
>>
>> Cheers,
>>
>> Richard
>

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > I've used master-next week or two ago (mostly to test bluez4 and python3
> > changes) and soon after that dropped all linux-yocto related changes
> > from it assuming that it's indeed cause for the issues I'm seeing, but
> > it's not and it's still failing with master as well (and my
> > jenkins/world builds are just small portion of my builds executed
> > elsewhere where I see similar issues).
> 
> Richard: How can we sort out the differences between the build
> environment that Martin uses versus what the autobuilder is showing?
> 
> There's nothing particularly complex happening during that build,
> it's a checkout and generation of a config.
> 
> I'm unable to reproduce any of the failures, and neither is the
> autobuilder.

This is a tough one and I'm struggling a little. We could try looking at
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
particular) as well as
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order

Martin, would you be able to share the above somewhere? I'm hoping this
would give us a clue as to what the difference is between the builds and
allow us to reproduce the problem.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]

I use tmpfs in most of my builds, so in most cases when I see the error
from the build, tmpfs is already gone (purged by next build executed on the
same sever).

On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and
> python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>

[-- Attachment #2: Type: text/html, Size: 2142 bytes --]

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]


> On May 6, 2015, at 8:33 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.

just for build sake to avoid full kernel builds, having a dummy kernel recipe should be another alternative


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On 2015-05-06 06:49 PM, Martin Jansa wrote:
> I use tmpfs in most of my builds, so in most cases when I see the error
> from the build, tmpfs is already gone (purged by next build executed on
> the same sever).

ross just found something like this in one of his local builds .. I'm
pretty sure I see the race.

Fix coming shortly, and then the bigger changes I was mentioning before
as well.

Cheers,

Bruce

>
> On Wed, May 6, 2015 at 11:32 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
>     On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
>     > On 2015-05-06 12:07 PM, Martin Jansa wrote:
>     > > I've used master-next week or two ago (mostly to test bluez4 and python3
>     > > changes) and soon after that dropped all linux-yocto related changes
>     > > from it assuming that it's indeed cause for the issues I'm seeing, but
>     > > it's not and it's still failing with master as well (and my
>     > > jenkins/world builds are just small portion of my builds executed
>     > > elsewhere where I see similar issues).
>     >
>     > Richard: How can we sort out the differences between the build
>     > environment that Martin uses versus what the autobuilder is showing?
>     >
>     > There's nothing particularly complex happening during that build,
>     > it's a checkout and generation of a config.
>     >
>     > I'm unable to reproduce any of the failures, and neither is the
>     > autobuilder.
>
>     This is a tough one and I'm struggling a little. We could try looking at
>     the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
>     particular) as well as
>     tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
>     Martin, would you be able to share the above somewhere? I'm hoping this
>     would give us a clue as to what the difference is between the builds and
>     allow us to reproduce the problem.
>
>     Cheers,
>
>     Richard
>
>
>

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

This series contains some changes that I've been gathering over the past
week. Nothing serious, just BSP mainline backports, configuration tweaks
to tiny (for usability) and a change to make aufs4 opt-in (versus always
on).

I've built and booted this for qemu* (standard and -rt).

Cheers,

Bruce

The following changes since commit e912c468875ffea7e8070cb7813bca262d1cbb0b:

  kbd: remove uclibc-stdarg.patch (2016-04-13 10:12:53 +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 (5):
  linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot
    read/write
  linux-yocto/4.1: mainline SPI backports
  linux-yocto/4.4: BXT enablement
  linux-yocto: tiny and pin ctrl config updates
  linux-yocto: make aufs4 optional

 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.1.bb      | 18 +++++++++---------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 18 +++++++++---------
 6 files changed, 26 insertions(+), 26 deletions(-)

-- 
2.5.0

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here's the latest set of changes to the 4.1 and 4.4 linux-yocto
kernel's. Nothing particularly exciting, mainline backports and
minor fixups.

Cheers,

Bruce

The following changes since commit 84cce1d49ddb75025ec454d758fbc8d369920122:

  e2fsprogs: remove the extra dot from the recipe filename (2016-06-21 13:00:17 +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 (5):
  linux-yocto/4.1: tpm2, pinctrl, powercap and watchdog backports
  linux-yocto/4.1: SPI, MFD, alsa and perf backports
  linux-yocto/4.1: driver, mmc and power backports
  linux-yocto/4.1: pstate backports
  linux-yocto/4.4: sensor driver backports

 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.1.bb      | 16 ++++++++--------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 16 ++++++++--------
 5 files changed, 19 insertions(+), 19 deletions(-)

-- 
2.5.0

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here's the latest batch of linux-yocto (4.1 and 4.4) changes. They are
-stable updates, a memory leak fix and configuration tweaks (in particular
the removal of debug kernel from the printk fragment).

This is a slight overlap with another series that I sent before, since I
noticed some mistakes in the 4.1 and 4.4-stable update commits .. so I
rephrased them.

Cheers,

Bruce

The following changes since commit 039f47ad197a9a53109c9f3deadd9c35e62c056d:

  uclibc: remove meta-yocto-bsp append (2016-07-26 08:56:32 +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 (5):
  linux-yocto/4.4: bump to v4.4.15
  linux-yocto/4.1: bump to v4.1.28
  linux-yocto/4.1: bug fixes and configuration changes
  linux-yocto/4.4: lx-dialog and mei bug fixes
  linux-yocto/4.4: mousedev and printk configuation streamlining

 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.1.bb      | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 20 ++++++++++----------
 6 files changed, 31 insertions(+), 31 deletions(-)

-- 
2.5.0

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

Here's the queued bug fixes for linux-yocto. It has khem's identified fixes
for the kernel selftest issues with the latest -stable udpates, as well as
some BSP fixes and config changes.

I ran this through the AB and everything came back green.

I've done this in multiple commits, so we'll have granularity to look
into individual fixes if we have trouble.

Cheers,

Bruce

The following changes since commit d5db9d12642e03a1d5cca5f1520dad5fcc9524c3:

  archiver.py: fix typo of "ARCHIVER_MIRROR_EXCLUDE" in comment (2020-03-24 16:39:40 +0000)

are available in the Git repository at:

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

Bruce Ashfield (5):
  linux-yocto/5.4: Revert "platform/x86: wmi: Destroy on cleanup rather
    than unregister"
  linux-yocto/5.4: fix kernel selftests
  linux-yocto/5.4: KVM: LAPIC: Mark hrtimer for period or oneshot mode
    to expire in hard interrupt context
  linux-yocto/5.4: ARM: 8918/2: only build return_address() if needed
  linux-yocto/5.4: configuration tweaks

 .../linux/linux-yocto-rt_5.4.bb               |  4 ++--
 .../linux/linux-yocto-tiny_5.4.bb             |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 20 +++++++++----------
 3 files changed, 15 insertions(+), 15 deletions(-)

-- 
2.19.1

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

Here are the -stable updates I've collected since m3 of dunfell. I ran
things through the autobuilder, and no new kernel issues were picked up.

The -dev bump is good for master, while all of the 5.4-stable bumps are
good for both master and dunfell.

Cheers,

Bruce

The following changes since commit 2e11d97b6c95e89aa1f9d3603a966c94c442469e:

  oeqa/qemurunner: Clean up failure handling (2020-04-26 14:00:51 +0100)

are available in the Git repository at:

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

Bruce Ashfield (5):
  linux-yocto/5.4: update to v5.4.28
  linux-yocto/5.4: update to v5.4.32
  linux-yocto/5.4: update to v5.4.34
  linux-yocto/5.4: update to v5.4.38
  linux-yocto-dev: bump to v5.7-rc

 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  2 +-
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 4 files changed, 19 insertions(+), 19 deletions(-)

-- 
2.19.1

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

Hi Bruce,

On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Hi all,
> 
> Here are the -stable updates I've collected since m3 of dunfell. I
> ran things through the autobuilder, and no new kernel issues were
> picked up.
> 
> The -dev bump is good for master, while all of the 5.4-stable bumps
> are good for both master and dunfell.

I pulled these into master-next and saw reproducibility issues. I
wondered why your test build didn't show it, turns out it also did:

https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024

2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException: 

AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk

master-next was:

https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900

and friends.

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On Mon, May 4, 2020 at 4:31 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > Here are the -stable updates I've collected since m3 of dunfell. I
> > ran things through the autobuilder, and no new kernel issues were
> > picked up.
> >
> > The -dev bump is good for master, while all of the 5.4-stable bumps
> > are good for both master and dunfell.
>
> I pulled these into master-next and saw reproducibility issues. I
> wondered why your test build didn't show it, turns out it also did:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
>
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
>
> AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
>

I don't see any changes in the kernels that would have triggered it,
but they never are obvious.

I unfortunately have no idea how to run reproducibility tests on the
kernels locally and my build server at home is brutally underpowered
for more than one core-image build per arch a day (hence the
autobuilder runs).

Is there a cut and paste se of instructions about the tests that I
could follow ?

Bruce

> master-next was:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
>
> and friends.
>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi Richard,

As discussed earlier, this is the pull request which contains a temporary
revert of the CONFIG_IKHEADERS config change that was causing the
periodic issues.

I added a kernel feature that can be used to enable the configuration from
a recipe, that way I won't leave anyone broken while I continue to debug,
since this still is a problem for anyone that is doing reproducible builds
and wants ikheaders.

This went through AB quick and came back green.

Bruce

The following changes since commit 392ba004f42be2fd9dcf121d3dfa5b414ff83f93:

  ref-manual: add PACKAGE_ADD_METADATA documentation (2020-05-27 11:05:04 +0100)

are available in the Git repository at:

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

Bruce Ashfield (5):
  linux-yocto/5.4: update to v5.4.42
  linux-yocto-rt/5.4: update to rt24
  linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels
  linux-yocto: gather reproducibility configs into a fragment
  linux-yocto/5.4: update to v5.4.43

 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 3 files changed, 18 insertions(+), 18 deletions(-)

-- 
2.19.1

[PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's my next set of collected changes for linux-yocto. I built and booted the
5.4 -stable bump .. and obviously it looks good.

I've also grabbed a pending devsrc change, that looks good to me.

Finally, I have a fix Khem sent for perf builds. I kept 5.4 and 5.8 separate
for that fix, so Steve can pick them up for Dunfell as appropriate.

Bruce

The following changes since commit d8f47a68a92802fc47f297de05a0f2817963a7ee:

  kernel: relocate copy of module.lds to module compilation task (2020-11-18 13:59:27 +0000)

are available in the Git repository at:

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

Bruce Ashfield (4):
  linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
    arches with 64bit time_t
  linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
    arches with 64bit time_t
  linux-yocto/5.8: ext4/tipc warning fixups
  linux-yocto/5.4: update to v5.4.78

INC@Cisco) (1):
  kernel-devsrc: improve reproducibility for arm64

 meta/recipes-kernel/linux/kernel-devsrc.bb    |  4 ++++
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-rt_5.8.bb               |  2 +-
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 .../linux/linux-yocto-tiny_5.8.bb             |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_5.8.bb  | 18 +++++++--------
 7 files changed, 34 insertions(+), 30 deletions(-)

-- 
2.19.1

[PATCH 1/5] kernel-devsrc: improve reproducibility for arm64

[Bruce Ashfield]

From: "INC@Cisco)" <INC@Cisco)>

.vdso-offsets.h.cmd contains command that was used to produce vdso-offsets.h.
It breaks reproducibility because it has an absolute path in it. There is no
any value to package such files so it can be dropped.

Signed-off-by: Denys Zagorui <dzagorui@cisco.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 8373c97a31..8a900ed182 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -119,6 +119,10 @@ do_install() {
 	# but without this file, we get a forced syncconfig run in v5.8+, which prompts and
 	# breaks workflows.
 	cp -a --parents include/generated/autoconf.h $kerneldir/build 2>/dev/null || :
+
+	if [ -e $kerneldir/include/generated/.vdso-offsets.h.cmd ]; then
+	    rm $kerneldir/include/generated/.vdso-offsets.h.cmd
+	fi
     )
 
     # now grab the chunks from the source tree that we need
-- 
2.19.1

[PATCH 2/5] linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit arches with 64bit time_t

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/5.4:

    356914747645 perf: Alias SYS_futex with SYS_futex_time64 on 32-bit arches with 64bit time_t

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../recipes-kernel/linux/linux-yocto-rt_5.4.bb |  2 +-
 .../linux/linux-yocto-tiny_5.4.bb              |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.4.bb   | 18 +++++++++---------
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 183acce226..4db2b33aef 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "e500e89811e268ab5c420744c41b10d12c9844a0"
+SRCREV_machine ?= "1fe1ef9c7272caf75d92b3e9166a0f29c4f06141"
 SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index f6190be8da..f6ed7f35ea 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -15,8 +15,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "2c7da912c6b5bd36d84f75e0aff4afd0814f1bd3"
-SRCREV_machine ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
+SRCREV_machine_qemuarm ?= "83d064534da33ab41108a786d917068f282a9bf2"
+SRCREV_machine ?= "356914747645db5ceba98b22acdfa060ef1764af"
 SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 23fc5ea819..0330a9d159 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,15 +12,15 @@ KBRANCH_qemux86  ?= "v5.4/standard/base"
 KBRANCH_qemux86-64 ?= "v5.4/standard/base"
 KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "dbac8d2939bca0a92226cfd55543331715dd642d"
-SRCREV_machine_qemuarm64 ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
-SRCREV_machine_qemumips ?= "819cf265755f21768f6bb98312cb568c6db8b1e8"
-SRCREV_machine_qemuppc ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
-SRCREV_machine_qemuriscv64 ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
-SRCREV_machine_qemux86 ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
-SRCREV_machine_qemux86-64 ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
-SRCREV_machine_qemumips64 ?= "bb9110d96ce8a2c56466e5b4314b93175af3d80d"
-SRCREV_machine ?= "d0096198f08dd2aa4222ef5480d2fcdaf520b65b"
+SRCREV_machine_qemuarm ?= "879db1ae1856cf5a9fe4609fdbcbe2e3c7bade5f"
+SRCREV_machine_qemuarm64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
+SRCREV_machine_qemumips ?= "190c3ce9c2dbc709c3dcf02d8cfa80adc8a063d2"
+SRCREV_machine_qemuppc ?= "356914747645db5ceba98b22acdfa060ef1764af"
+SRCREV_machine_qemuriscv64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
+SRCREV_machine_qemux86 ?= "356914747645db5ceba98b22acdfa060ef1764af"
+SRCREV_machine_qemux86-64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
+SRCREV_machine_qemumips64 ?= "98b1fc2eafc28e5c198e23579e38a76626c66182"
+SRCREV_machine ?= "356914747645db5ceba98b22acdfa060ef1764af"
 SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
 
 # remap qemuarm to qemuarma15 for the 5.4 kernel
-- 
2.19.1

[PATCH 3/5] linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit arches with 64bit time_t

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/5.8:

    52b840afae05 perf: Alias SYS_futex with SYS_futex_time64 on 32-bit arches with 64bit time_t

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../recipes-kernel/linux/linux-yocto-rt_5.8.bb |  2 +-
 .../linux/linux-yocto-tiny_5.8.bb              |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.8.bb   | 18 +++++++++---------
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
index 203ddf6684..c2d627acb7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
+SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
index f37f525cc3..31a84f3972 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
@@ -15,8 +15,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "aa614dcf182db126013b255968ab125afd96eb88"
-SRCREV_machine ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
+SRCREV_machine_qemuarm ?= "3e9aa72b02cf7d04096e367c99d503cd1d26cc6c"
+SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.8.bb b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
index c0cdffce73..c6fb9e9f86 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
@@ -12,15 +12,15 @@ KBRANCH_qemux86  ?= "v5.8/standard/base"
 KBRANCH_qemux86-64 ?= "v5.8/standard/base"
 KBRANCH_qemumips64 ?= "v5.8/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "cd6c8c74317d2f9504c25e28e37f4140deec2d19"
-SRCREV_machine_qemuarm64 ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
-SRCREV_machine_qemumips ?= "c610a204d0821f5abc253e72894fd32b41b92db3"
-SRCREV_machine_qemuppc ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
-SRCREV_machine_qemuriscv64 ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
-SRCREV_machine_qemux86 ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
-SRCREV_machine_qemux86-64 ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
-SRCREV_machine_qemumips64 ?= "86cc0d9a3f6751ada12fa4630b3e3c23221d6da7"
-SRCREV_machine ?= "64fd51cbe98ae4a0e05e59ed9abd9135f1b4cf64"
+SRCREV_machine_qemuarm ?= "0c6d276c75233f9b8d05103ff652676a2c271868"
+SRCREV_machine_qemuarm64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemumips ?= "4c07d59936f8e28eadecab8f56ef14726f77ccb8"
+SRCREV_machine_qemuppc ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemuriscv64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemux86 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemux86-64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemumips64 ?= "2224bf83cf372bb729583dfb93ad28abba9905fd"
+SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 # remap qemuarm to qemuarma15 for the 5.8 kernel
-- 
2.19.1

[PATCH 4/5] linux-yocto/5.8: ext4/tipc warning fixups

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/5.8:

    3c5d210805d6 tipc: fix -Wstringop-truncation warnings
    cc89fd77c248 ext4: fix -Wstringop-truncation warnings

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../recipes-kernel/linux/linux-yocto-rt_5.8.bb |  2 +-
 .../linux/linux-yocto-tiny_5.8.bb              |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_5.8.bb   | 18 +++++++++---------
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
index c2d627acb7..033dfc76a2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
index 31a84f3972..50cee07620 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb
@@ -15,8 +15,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "3e9aa72b02cf7d04096e367c99d503cd1d26cc6c"
-SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemuarm ?= "9509db6e3ed6a23b1f7495b53248d1cbfe22710b"
+SRCREV_machine ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.8.bb b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
index c6fb9e9f86..af576891e2 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.8.bb
@@ -12,15 +12,15 @@ KBRANCH_qemux86  ?= "v5.8/standard/base"
 KBRANCH_qemux86-64 ?= "v5.8/standard/base"
 KBRANCH_qemumips64 ?= "v5.8/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "0c6d276c75233f9b8d05103ff652676a2c271868"
-SRCREV_machine_qemuarm64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
-SRCREV_machine_qemumips ?= "4c07d59936f8e28eadecab8f56ef14726f77ccb8"
-SRCREV_machine_qemuppc ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
-SRCREV_machine_qemuriscv64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
-SRCREV_machine_qemux86 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
-SRCREV_machine_qemux86-64 ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
-SRCREV_machine_qemumips64 ?= "2224bf83cf372bb729583dfb93ad28abba9905fd"
-SRCREV_machine ?= "52b840afae058fb20ce69ff5af811f8582b3bb5a"
+SRCREV_machine_qemuarm ?= "14b463d0e5c1e2ff354244420f9bbc7f0ab80533"
+SRCREV_machine_qemuarm64 ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
+SRCREV_machine_qemumips ?= "8d8d9afb396f154f366f32948fdff3cf4e269841"
+SRCREV_machine_qemuppc ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
+SRCREV_machine_qemuriscv64 ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
+SRCREV_machine_qemux86 ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
+SRCREV_machine_qemux86-64 ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
+SRCREV_machine_qemumips64 ?= "01a02b058f9a8941032b298b8d25c673526152f4"
+SRCREV_machine ?= "3c5d210805d61bea8f8a8081e0e3a89ea8a61f3f"
 SRCREV_meta ?= "7883b60d324029d26020c0b3f826b35c52fd9674"
 
 # remap qemuarm to qemuarma15 for the 5.8 kernel
-- 
2.19.1

[PATCH 5/5] linux-yocto/5.4: update to v5.4.78

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

    315443293a2d Linux 5.4.78
    9fda2e762498 Convert trailing spaces and periods in path components
    ebc24aeb8694 net: sch_generic: fix the missing new qdisc assignment bug
    c5cf5c7b585c perf/core: Fix race in the perf_mmap_close() function
    c6b1616f5472 perf scripting python: Avoid declaring function pointers with a visibility attribute
    b74fe3186471 x86/speculation: Allow IBPB to be conditionally enabled on CPUs with always-on STIBP
    6958fbd52e79 powerpc/603: Always fault when _PAGE_ACCESSED is not set
    5af9d48acbee drm/i915: Correctly set SFC capability for video engines
    6fcf4141b9a2 r8169: fix potential skb double free in an error path
    78f6fac0814e tipc: fix memory leak in tipc_topsrv_start()
    c59039a088bd net/x25: Fix null-ptr-deref in x25_connect
    7e332a5c0e2c net: Update window_clamp if SOCK_RCVBUF is set
    25786fb512f7 net: udp: fix UDP header access on Fast/frag0 UDP GRO
    016e70d176ff net/af_iucv: fix null pointer dereference on shutdown
    22ee23fe1cc9 IPv6: Set SIT tunnel hard_header_len to zero
    98901bff58d9 swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
    2cd21fe5bcc4 pinctrl: amd: fix incorrect way to disable debounce filter
    fa76dd3c1df3 pinctrl: amd: use higher precision for 512 RtcClk
    c6a6168a31e1 drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
    974e3a7002a0 don't dump the threads that had been already exiting when zapped.
    039c8dcd2b15 mmc: renesas_sdhi_core: Add missing tmio_mmc_host_free() at remove
    e1d706eeeaf7 mmc: sdhci-of-esdhc: Handle pulse width detection erratum for more SoCs
    2a6cba6d3d72 gpio: pcie-idio-24: Enable PEX8311 interrupts
    7b6790ae3a94 gpio: pcie-idio-24: Fix IRQ Enable Register value
    819bf3b0d969 gpio: pcie-idio-24: Fix irq mask when masking
    68dae71b7cde selinux: Fix error return code in sel_ib_pkey_sid_slow()
    33e53f2cac19 btrfs: fix potential overflow in cluster_pages_for_defrag on 32bit arch
    9de4ffb70150 ocfs2: initialize ip_next_orphan
    ac18b128cfd6 reboot: fix overflow parsing reboot cpu number
    fa6265f8fb9e Revert "kernel/reboot.c: convert simple_strtoul to kstrtoint"
    bd4d106f3122 mm/slub: fix panic in slab_alloc_node()
    84778a43ae59 jbd2: fix up sparse warnings in checkpoint code
    2192d905df0d futex: Don't enable IRQs unconditionally in put_pi_state()
    761fb6829238 mei: protect mei_cl_mtu from null dereference
    e2b2c390ec9e virtio: virtio_console: fix DMA memory allocation for rproc serial
    57626d77ef1e xhci: hisilicon: fix refercence leak in xhci_histb_probe
    cbad9668929c usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
    f988e9c85cfb uio: Fix use-after-free in uio_unregister_device()
    1654bf2d9f0e thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
    06c1895fe71b thunderbolt: Fix memory leak if ida_simple_get() fails in enumerate_services()
    11c14da8d005 KVM: arm64: Don't hide ID registers from userspace
    2033dd885297 btrfs: dev-replace: fail mount if we don't have replace item with target device
    5af9630036ef btrfs: fix min reserved size calculation in merge_reloc_root
    8266c23124c1 btrfs: ref-verify: fix memory leak in btrfs_ref_tree_mod
    062c9b04f6eb ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
    a6ca4c7ec44c ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA
    52e3a55bc253 erofs: derive atime instead of leaving it empty
    09b0d47b7952 perf: Fix get_recursion_context()
    70867a9dbf57 vrf: Fix fast path output packet handling with async Netfilter rules
    2ab9c76986e4 cosa: Add missing kfree in error path of cosa_write
    c0a6cc9e11f4 of/address: Fix of_node memory leak in of_dma_is_coherent
    f10d238aad93 xfs: fix a missing unlock on error in xfs_fs_map_blocks
    0e2ad69bd4b5 lan743x: fix "BUG: invalid wait context" when setting rx mode
    b45f52a20879 xfs: fix brainos in the refcount scrubber's rmap fragment processor
    7cbf708b1b9a xfs: fix rmap key and record comparison functions
    3bd97b33be41 xfs: set the unwritten bit in rmap lookup flags in xchk_bmap_get_rmapextents
    08e213bef291 xfs: fix flags argument to rmap lookup when converting shared file rmaps
    a8ee686597fb igc: Fix returning wrong statistics
    81dcfdb9a015 nbd: fix a block_device refcount leak in nbd_release
    c602ad2b52dc bpf: Zero-fill re-used per-cpu map element
    dfcb33773877 SUNRPC: Fix general protection fault in trace_rpc_xdr_overflow()
    b9e8f9d139bd net/mlx5: Fix deletion of duplicate rules
    e74e514c8cca pinctrl: aspeed: Fix GPI only function problem.
    d2e61c5202e6 bpf: Don't rely on GCC __attribute__((optimize)) to disable GCSE
    443ae3655f8c ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
    c0be7a34c889 pinctrl: intel: Set default bias in case no particular value given
    88ccabbd2066 mfd: sprd: Add wakeup capability for PMIC IRQ
    58953e87343d tick/common: Touch watchdog in tick_unfreeze() on all CPUs
    3322f7289e50 spi: bcm2835: remove use of uninitialized gpio flags variable
    572e545d80ea tpm_tis: Disable interrupts on ThinkPad T490s
    713a3a94bee0 i2c: sh_mobile: implement atomic transfers
    37a048d790c3 riscv: Set text_offset correctly for M-Mode
    6d8b43376990 selftests: proc: fix warning: _GNU_SOURCE redefined
    ab10b7def421 amd/amdgpu: Disable VCN DPG mode for Picasso
    4faa1fabc645 i2c: mediatek: move dma reset before i2c reset
    b66c7cdedd1e vfio/pci: Bypass IGD init in case of -ENODEV
    c6be53caf1c8 vfio: platform: fix reference leak in vfio_platform_open
    4d6f536e34d6 s390/smp: move rcu_cpu_starting() earlier
    984d77507439 iommu/amd: Increase interrupt remapping table limit to 512 entries
    a889cd3d350d nvme-tcp: avoid repeated request completion
    9d14f5225dbb nvme-rdma: avoid repeated request completion
    531b55cce9cd nvme-tcp: avoid race between time out and tear down
    d0e888a20dfd nvme-rdma: avoid race between time out and tear down
    0ca279c859d7 nvme: introduce nvme_sync_io_queues
    c473b3e56c1d scsi: mpt3sas: Fix timeouts observed while reenabling IRQ
    b61e157d9f64 scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
    bf1cedc12f58 tracing: Fix the checking of stackidx in __ftrace_trace_stack
    e57c04697030 cfg80211: regulatory: Fix inconsistent format argument
    a3f0db0d2320 cfg80211: initialize wdev data earlier
    67bb2e4d41de mac80211: fix use of skb payload instead of header
    c1cbb64c100d drm/amd/pm: do not use ixFEATURE_STATUS for checking smc running
    48083640a47b drm/amd/pm: perform SMC reset on suspend/hibernation
    f449b902badb drm/amdgpu: perform srbm soft reset always on SDMA resume
    7f6df0b085ce scsi: hpsa: Fix memory leak in hpsa_init_one()
    325455358e54 gfs2: check for live vs. read-only file system in gfs2_fitrim
    edeff05a1f10 gfs2: Add missing truncate_inode_pages_final for sd_aspace
    99dcfc517d17 gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
    42eaa22aaf2e ALSA: hda: Reinstate runtime_allow() for all hda controllers
    0a4c091673ca ALSA: hda: Separate runtime and system suspend
    9b7e6b670df7 selftests: pidfd: fix compilation errors due to wait.h
    9110e2f2633d selftests/ftrace: check for do_sys_openat2 in user-memory test
    1737ea0c5775 usb: gadget: goku_udc: fix potential crashes in probe
    e60490354191 opp: Reduce the size of critical section in _opp_table_kref_release()
    fe2dc1093c61 usb: dwc3: pci: add support for the Intel Alder Lake-S
    e22142a9a2a9 ASoC: cs42l51: manage mclk shutdown delay
    0fc0befe0bfa ASoC: qcom: sdm845: set driver name correctly
    b668352c4aad ath9k_htc: Use appropriate rs_datalen type
    42501604363f KVM: x86: don't expose MSR_IA32_UMWAIT_CONTROL unconditionally
    d2cef3bae14b KVM: arm64: ARM_SMCCC_ARCH_WORKAROUND_1 doesn't return SMCCC_RET_NOT_REQUIRED
    213e1238cacc random32: make prandom_u32() output unpredictable
    327af342ca9b tpm: efi: Don't create binary_bios_measurements file for an empty log
    0685eb84ad56 xfs: fix scrub flagging rtinherit even if there is no rt device
    2f6cbef32718 xfs: flush new eof page on truncate to avoid post-eof corruption
    66ce8bfad6f6 can: flexcan: flexcan_remove(): disable wakeup completely
    0b657367309e can: flexcan: remove FLEXCAN_QUIRK_DISABLE_MECR quirk for LS1021A
    56c56af0a3a1 can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback is on
    a23ee9956612 can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
    44b2c4beff8a can: peak_usb: add range checking in decode operations
    d6c34afab0ed can: xilinx_can: handle failure cases of pm_runtime_get_sync
    51920ca7519c can: ti_hecc: ti_hecc_probe(): add missed clk_disable_unprepare() in error path
    b9c4a9a07c4a can: j1939: j1939_sk_bind(): return failure if netdev is down
    0ab4c839409a can: j1939: swap addr and pgn in the send example
    5bde65abe166 can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
    183f1af506fe can: dev: __can_get_echo_skb(): fix real payload length return value for RTR frames
    ab46748bf988 can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context
    3d0954767918 can: rx-offload: don't call kfree_skb() from IRQ context
    e201588fad54 afs: Fix warning due to unadvanced marshalling pointer
    9946509a027b iommu/vt-d: Fix a bug for PDP check in prq_event_thread
    2825a5bf3ca5 ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
    22901751d269 perf tools: Add missing swap for ino_generation
    b36f78fd48e9 perf trace: Fix segfault when trying to trace events by cgroup
    d261d0bd9066 powerpc/eeh_cache: Fix a possible debugfs deadlock
    1c8fe343a79d netfilter: ipset: Update byte and packet counters regardless of whether they match
    ad017cf5dace netfilter: nf_tables: missing validation from the abort path
    56907fa27b94 netfilter: use actual socket sk rather than skb sk when routing harder
    6234710dc634 xfs: set xefi_discard when creating a deferred agfl free log intent item
    933f911136e2 ASoC: codecs: wcd9335: Set digital gain range correctly
    5cb904da85ed net: xfrm: fix a race condition during allocing spi
    4e438ca1b629 hv_balloon: disable warning when floor reached
    bb2b60242c8e genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
    bb8c6bd53cc0 ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function
    a8ec66026dd8 btrfs: reschedule when cloning lots of extents
    0ee771e96954 btrfs: sysfs: init devices outside of the chunk_mutex
    c58fa93b1409 btrfs: tracepoints: output proper root owner for trace_find_free_extent()
    e24516cf62f9 usb: dwc3: gadget: Reclaim extra TRBs after request completion
    ab031673e2ab usb: dwc3: gadget: Continue to process pending requests
    504cfb5e3bca PCI: qcom: Make sure PCIe is reset before init for rev 2.1.0
    9dfbc2f82ac8 KVM: arm64: Force PTE mapping on fault resulting in a device mapping
    95fda70d3955 nbd: don't update block size after device is started
    160777b19b86 time: Prevent undefined behaviour in timespec64_to_ns()
    5a39fb2f22fd drm/i915/gem: Flush coherency domains on first set-domain-ioctl
    2544d06afd8d Linux 5.4.77
    19f6d91bdad4 powercap: restrict energy meter to root access
    ec9c6b417e27 Linux 5.4.76
    c3d60c695712 arm64: dts: marvell: espressobin: Add ethernet switch aliases
    b7f7474b3921 perf/core: Fix a memory leak in perf_event_parse_addr_filter()
    21ab13af8c50 xfs: flush for older, xfs specific ioctls
    258d01b1577e PM: runtime: Resume the device earlier in __device_release_driver()
    37f75c6aa8dd PM: runtime: Drop pm_runtime_clean_up_links()
    874dfb5c6aa3 PM: runtime: Drop runtime PM references to supplier on link removal
    fbfca92c7840 ARC: stack unwinding: avoid indefinite looping
    d61edc06002f drm/panfrost: Fix a deadlock between the shrinker and madvise path
    b9d91fa92164 usb: mtu3: fix panic in mtu3_gadget_stop()
    b0d03a1bdb3c USB: Add NO_LPM quirk for Kingston flash drive
    290fcf3e0c0c usb: dwc3: ep0: Fix delay status handling
    86875e1d6426 tty: serial: fsl_lpuart: LS1021A has a FIFO size of 16 words, like LS1028A
    8febdfb5973d tty: serial: fsl_lpuart: add LS1028A support
    d5d3cca9d61f USB: serial: option: add Telit FN980 composition 0x1055
    7f7be9341b86 USB: serial: option: add LE910Cx compositions 0x1203, 0x1230, 0x1231
    b7f74775c2bb USB: serial: option: add Quectel EC200T module support
    9d34dbab6ef4 USB: serial: cyberjack: fix write-URB completion race
    62c4b2b21e3b serial: txx9: add missing platform_driver_unregister() on error in serial_txx9_init
    085fc4784e4b serial: 8250_mtk: Fix uart_get_baud_rate warning
    b33a1039564c s390/pkey: fix paes selftest failure with paes and pkey static build
    beeb658cfd35 fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent
    642181fe3567 vt: Disable KD_FONT_OP_COPY
    cfd9d7137759 Revert "coresight: Make sysfs functional on topologies with per core sink"
    8ee6a0f25457 arm64/smp: Move rcu_cpu_starting() earlier
    eceb94287dbf drm/nouveau/gem: fix "refcount_t: underflow; use-after-free"
    7d0de6f87257 drm/nouveau/nouveau: fix the start/end range for migration
    4dab0fd40323 usb: cdns3: gadget: suspicious implicit sign extension
    937753df482c ACPI: NFIT: Fix comparison to '-ENXIO'
    16476c2b26ca drm/vc4: drv: Add error handding for bind
    a04cec1dd293 nvmet: fix a NULL pointer dereference when tracing the flush command
    8c9c03432500 nvme-rdma: handle unexpected nvme completion data length
    2fd9e60760ef vsock: use ns_capable_noaudit() on socket create
    2149aa583068 scsi: ibmvscsi: Fix potential race after loss of transport
    1247f4e29188 drm/amdgpu: add DID for navi10 blockchain SKU
    fd4fb5080725 scsi: core: Don't start concurrent async scan on same host
    3c52715ceaae blk-cgroup: Pre-allocate tree node on blkg_conf_prep
    f77756ea6641 blk-cgroup: Fix memleak on error path
    914fc5524261 drm/sun4i: frontend: Fix the scaler phase on A33
    f743f73f42a7 drm/sun4i: frontend: Reuse the ch0 phase for RGB formats
    6d7b41a67687 drm/sun4i: frontend: Rework a bit the phase data
    147e3743cf7a of: Fix reserved-memory overlap detection
    6e02c29e4ac4 x86/kexec: Use up-to-dated screen_info copy to fill boot params
    3283d4d78412 arm64: dts: meson: add missing g12 rng clock
    69e0e917c7c8 ARM: dts: sun4i-a10: fix cpu_alert temperature
    2716e78a6486 futex: Handle transient "ownerless" rtmutex state correctly
    ec5f524e0293 tracing: Fix out of bounds write in get_trace_buf
    9f6883fce694 spi: bcm2835: fix gpio cs level inversion
    f352cca84625 regulator: defer probe when trying to get voltage from unresolved supply
    a69af5baed80 ftrace: Handle tracing when switching between context
    3058420f40fb ftrace: Fix recursion check for NMI test
    cfaf010cf345 mtd: spi-nor: Don't copy self-pointing struct around
    aef59b5e5bdf ring-buffer: Fix recursion protection transitions between interrupt context
    2cd71743e7ff gfs2: Wake up when sd_glock_disposal becomes zero
    d2286457bd83 mm: always have io_remap_pfn_range() set pgprot_decrypted()
    1b8490d6b809 kthread_worker: prevent queuing delayed work from timer_fn when it is being canceled
    b1d16be4f2f4 lib/crc32test: remove extra local_irq_disable/enable
    c1f729c7dec0 mm: mempolicy: fix potential pte_unmap_unlock pte error
    f7c2913d606b ALSA: usb-audio: Add implicit feedback quirk for MODX
    26a871cf86cb ALSA: usb-audio: Add implicit feedback quirk for Qu-16
    a46e830d017e ALSA: usb-audio: add usb vendor id as DSD-capable for Khadas devices
    65457e345f3c ALSA: usb-audio: Add implicit feedback quirk for Zoom UAC-2
    72ce616ed55a ALSA: hda/realtek - Enable headphone for ASUS TM420
    f7d0f7242405 ALSA: hda/realtek - Fixed HP headset Mic can't be detected
    61402d61a2af Fonts: Replace discarded const qualifier
    e5ea79bb19f8 sfp: Fix error handing in sfp_probe()
    9b5458effeee sctp: Fix COMM_LOST/CANT_STR_ASSOC err reporting on big-endian platforms
    26ffb8916059 powerpc/vnic: Extend "failover pending" window
    92e65059beda net: usb: qmi_wwan: add Telit LE910Cx 0x1230 composition
    8e3c047f814b ip_tunnel: fix over-mtu packet send fail without TUNNEL_DONT_FRAGMENT flags
    ac343efb572c ionic: check port ptr before use
    6ef3bcc25a3e gianfar: Account for Tx PTP timestamp in the skb headroom
    5b66a5b6a9e2 gianfar: Replace skb_realloc_headroom with skb_cow_head for PTP
    7bf7b7c385a1 chelsio/chtls: fix always leaking ctrl_skb
    14d755a4815e chelsio/chtls: fix memory leaks caused by a race
    57bb59f9d8fb cadence: force nonlinear buffers to be cloned
    1695fca8a923 ptrace: fix task_join_group_stop() for the case when current is traced
    76e5bba75a63 tipc: fix use-after-free in tipc_bcast_get_mode
    ca16a42f5f0d arm64: Change .weak to SYM_FUNC_START_WEAK_PI for arch/arm64/lib/mem*.S
    d94589900d98 arm64: lib: Use modern annotations for assembly functions
    3e7050661d95 arm64: asm: Add new-style position independent function annotations
    840d8c9b3e5f linkage: Introduce new macros for assembler symbols
    1ca84322ab5b ASoC: Intel: Skylake: Add alternative topology binary name
    e05dfcff26e9 drm/i915: Drop runtime-pm assert from vgpu io accessors
    d321f127eb51 drm/i915/gt: Delay execlist processing for tgl
    5bcd18bf8082 drm/i915: Break up error capture compression loops with cond_resched()

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 4db2b33aef..104ada2db5 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "1fe1ef9c7272caf75d92b3e9166a0f29c4f06141"
-SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
+SRCREV_machine ?= "97576fb7447efba82eb025bde3ae9ceb29939d5e"
+SRCREV_meta ?= "d626f9108d590d41e82b97cbffc380aa699e86e1"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "5.4.75"
+LINUX_VERSION ?= "5.4.78"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index f6ed7f35ea..d8784c49ad 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "5.4.75"
+LINUX_VERSION ?= "5.4.78"
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "83d064534da33ab41108a786d917068f282a9bf2"
-SRCREV_machine ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
+SRCREV_machine_qemuarm ?= "6cf3b1d30bc7ac9bd86190129b3cbbdd04b8b236"
+SRCREV_machine ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_meta ?= "d626f9108d590d41e82b97cbffc380aa699e86e1"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 0330a9d159..c24e5ddc87 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86  ?= "v5.4/standard/base"
 KBRANCH_qemux86-64 ?= "v5.4/standard/base"
 KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "879db1ae1856cf5a9fe4609fdbcbe2e3c7bade5f"
-SRCREV_machine_qemuarm64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_machine_qemumips ?= "190c3ce9c2dbc709c3dcf02d8cfa80adc8a063d2"
-SRCREV_machine_qemuppc ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_machine_qemuriscv64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_machine_qemux86 ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_machine_qemux86-64 ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_machine_qemumips64 ?= "98b1fc2eafc28e5c198e23579e38a76626c66182"
-SRCREV_machine ?= "356914747645db5ceba98b22acdfa060ef1764af"
-SRCREV_meta ?= "8d0ed83a864cc91eef4d2abbc90f13d4ecd1c213"
+SRCREV_machine_qemuarm ?= "b3bafed66cf1be24caaa9c876d7d9a8298df831b"
+SRCREV_machine_qemuarm64 ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_machine_qemumips ?= "36c2a0b1caef0b2dd6b5777d1939c383238536a8"
+SRCREV_machine_qemuppc ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_machine_qemuriscv64 ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_machine_qemux86 ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_machine_qemux86-64 ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_machine_qemumips64 ?= "971a3cedf9a2a7774fa072b9a13380fb59fd605b"
+SRCREV_machine ?= "370ef947d5b1470e858bae5a300110566c994b9f"
+SRCREV_meta ?= "d626f9108d590d41e82b97cbffc380aa699e86e1"
 
 # remap qemuarm to qemuarma15 for the 5.4 kernel
 # KMACHINE_qemuarm ?= "qemuarma15"
@@ -30,7 +30,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
-LINUX_VERSION ?= "5.4.75"
+LINUX_VERSION ?= "5.4.78"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
 DEPENDS += "openssl-native util-linux-native"
-- 
2.19.1

Re: [OE-core] [PATCH 0/5] linux-yocto: consolidated pull request

[Steve Sakoman]

On Thu, Nov 19, 2020 at 9:18 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Richard,
>
> Here's my next set of collected changes for linux-yocto. I built and booted the
> 5.4 -stable bump .. and obviously it looks good.
>
> I've also grabbed a pending devsrc change, that looks good to me.
>
> Finally, I have a fix Khem sent for perf builds. I kept 5.4 and 5.8 separate
> for that fix, so Steve can pick them up for Dunfell as appropriate.

Thanks :-)

Steve

> Bruce
>
> The following changes since commit d8f47a68a92802fc47f297de05a0f2817963a7ee:
>
>   kernel: relocate copy of module.lds to module compilation task (2020-11-18 13:59:27 +0000)
>
> are available in the Git repository at:
>
>   git://git.yoctoproject.org/poky-contrib zedd/kernel
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (4):
>   linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
>     arches with 64bit time_t
>   linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
>     arches with 64bit time_t
>   linux-yocto/5.8: ext4/tipc warning fixups
>   linux-yocto/5.4: update to v5.4.78
>
> INC@Cisco) (1):
>   kernel-devsrc: improve reproducibility for arm64
>
>  meta/recipes-kernel/linux/kernel-devsrc.bb    |  4 ++++
>  .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
>  .../linux/linux-yocto-rt_5.8.bb               |  2 +-
>  .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
>  .../linux/linux-yocto-tiny_5.8.bb             |  4 ++--
>  meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +++++++++----------
>  meta/recipes-kernel/linux/linux-yocto_5.8.bb  | 18 +++++++--------
>  7 files changed, 34 insertions(+), 30 deletions(-)
>
> --
> 2.19.1
>
>
> 
>

[PATCH 0/5] linux-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's the latest round of configuration and -stable udpates that
I've collected.

Nothing major, but hopefully the virtio patches will help some of
the AB issues.

Bruce

The following changes since commit da95831d91b1265ecaee5bbfaeb1caaa2c290838:

  scons: Pass MAXLINELENGTH to scons invocation (2023-01-31 17:11:07 +0000)

are available in the Git repository at:

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

Bruce Ashfield (5):
  linux-yocto/6.1: update to v6.1.7
  linux-yocto/5.15: update to v5.15.89
  linux-yocto/6.1: cfg: remove depreciated configs
  linux-yocto/6.1: update to v6.1.9
  linux-yocto/5.15: update to v5.15.91

 .../linux/linux-yocto-rt_5.15.bb              |  6 ++---
 .../linux/linux-yocto-rt_6.1.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.15.bb            |  6 ++---
 .../linux/linux-yocto-tiny_6.1.bb             |  6 ++---
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_6.1.bb  | 26 +++++++++----------
 6 files changed, 38 insertions(+), 38 deletions(-)

-- 
2.34.1

[PATCH 0/5] linux-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

This is mainly a v3 of the 6.10 introduction series, but I've
also included a 6.6 version bump and 6.11 for -dev.

This should fix the:

  - trap seen on multiple machines with 6.10.3, I've disabled a
    NFS option that was introduced in .3 (and shoulldn't have
    been)
  - I've updated -rt to fix the build issue

As I mentioned in another reply, the config warning that showed
up on meta-virt shouldn't have happened, since the Kconfig option
in question was removed from the kernel-cache about three weeks
ago. If that warning comes back, I'll want to have a look at the
SRCREVs being built to see what is going on!

Bruce

The following changes since commit b997e4dc9cce85afeddf5c53b094e00379f7caae:

  ffmpeg: fix build with binutils 2.43 on arm with commerical codecs (2024-08-09 22:33:38 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto-dev: bump to v6.11
  linux-yocto-rt/6.10: update to -rt14
  linux-yocto/6.10: cfg: disable nfsd legacy client tracking
  linux-yocto/6.6: update to v6.6.44
  poky/poky-tiny: bump preferred version to 6.10

 meta-poky/conf/distro/poky-tiny.conf          |  2 +-
 meta-poky/conf/distro/poky.conf               |  4 +--
 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  4 +--
 .../linux/linux-yocto-rt_6.10.bb              |  4 +--
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.10.bb            |  2 +-
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.10.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 9 files changed, 29 insertions(+), 29 deletions(-)

-- 
2.39.2

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Richard Purdie]

Hi Bruce,

On Sun, 2024-08-11 at 14:04 -0400, bruce.ashfield@gmail.com wrote:
> This is mainly a v3 of the 6.10 introduction series, but I've
> also included a 6.6 version bump and 6.11 for -dev.
> 
> This should fix the:
> 
>   - trap seen on multiple machines with 6.10.3, I've disabled a
>     NFS option that was introduced in .3 (and shoulldn't have
>     been)
>   - I've updated -rt to fix the build issue

Thanks, those are indeed fixed :)

> As I mentioned in another reply, the config warning that showed
> up on meta-virt shouldn't have happened, since the Kconfig option
> in question was removed from the kernel-cache about three weeks
> ago. If that warning comes back, I'll want to have a look at the
> SRCREVs being built to see what is going on!

The meta-virt warnings are still there:

https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3487/steps/13/logs/stdio

(for qemuarm, qemux86-64, qemuarm64)

There are a couple of genericarm64 warnings:

https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/727
https://autobuilder.yoctoproject.org/typhoon/#/builders/165/builds/723

The meta-aws and meta-arm issues are fixed.

We're probably at the point this should merge and the remaining bits
get fixed as we sort them out as we're down to warnings?

Cheers,

Richard

Re: [PATCH 0/5] linux-yocto: consolidated pull request

[Bruce Ashfield]

On Mon, Aug 12, 2024 at 5:47 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Sun, 2024-08-11 at 14:04 -0400, bruce.ashfield@gmail.com wrote:
> > This is mainly a v3 of the 6.10 introduction series, but I've
> > also included a 6.6 version bump and 6.11 for -dev.
> >
> > This should fix the:
> >
> >   - trap seen on multiple machines with 6.10.3, I've disabled a
> >     NFS option that was introduced in .3 (and shoulldn't have
> >     been)
> >   - I've updated -rt to fix the build issue
>
> Thanks, those are indeed fixed :)
>
> > As I mentioned in another reply, the config warning that showed
> > up on meta-virt shouldn't have happened, since the Kconfig option
> > in question was removed from the kernel-cache about three weeks
> > ago. If that warning comes back, I'll want to have a look at the
> > SRCREVs being built to see what is going on!
>
> The meta-virt warnings are still there:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3487/steps/13/logs/stdio

I finally know what this is, I can fix it in meta-virt, so it will gone shortly.

>
> (for qemuarm, qemux86-64, qemuarm64)
>
> There are a couple of genericarm64 warnings:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/727
> https://autobuilder.yoctoproject.org/typhoon/#/builders/165/builds/723

Confirmed. I see the same here. If someone needs my help on them,
I can send patches, but I've stayed away for now since I don't know
what is already in progress.

>
> The meta-aws and meta-arm issues are fixed.
>
> We're probably at the point this should merge and the remaining bits
> get fixed as we sort them out as we're down to warnings?

Agreed. Let's start seeing if there are more subtle issues with the kernel
under the ptest/AB load that will only pop out with some repeated
execution.

Bruce

>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II