Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Graydon, Tracy
On 05/24/16, 4:30 PM, "Randle, William C" wrote: >On Tue, 2016-05-24 at 16:06 -0700, Graydon, Tracy wrote: >> Get rid of the extraneous DL_BASE line. It's not used and should have >> been removed when I fixed the eclipse-plugin release path. >> >> Signed-off-by:

Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Randle, William C
On Tue, 2016-05-24 at 16:06 -0700, Graydon, Tracy wrote: > Get rid of the extraneous DL_BASE line. It's not used and should have > been removed when I fixed the eclipse-plugin release path. > > Signed-off-by: Graydon, Tracy > --- >  bin/release_scripts/release.py | 1 - >

[yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Graydon, Tracy
Get rid of the extraneous DL_BASE line. It's not used and should have been removed when I fixed the eclipse-plugin release path. Signed-off-by: Graydon, Tracy --- bin/release_scripts/release.py | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Graydon, Tracy
On 05/24/16, 8:46 AM, "Randle, William C" wrote: >On Mon, 2016-05-23 at 19:07 -0700, Graydon, Tracy wrote: >> Fixed the path for the publishing of the eclipse plugins. They were >> going to the wrong subdirectory under downloads. >> >> Signed-off-by: Graydon, Tracy

[yocto] [yocto-autobuilder][PATCH] bin/release_scripts/relnotes.py

2016-05-24 Thread Graydon, Tracy
Works better for all major/point releases if the poky version isn't hardcoded to 14.0.1. Fixed that. Signed-off-by: Graydon, Tracy --- bin/release_scripts/relnotes.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/release_scripts/relnotes.py

[linux-yocto] [PATCH 4/6] intel-quark-tiny: Add common-pc branch to match KBRANCH

2016-05-24 Thread Tom Zanussi
Because meta-intel linux-yocto-tiny specifies a KBRANCH of standard/tiny/common-pc, we get the below warning since the board metadata doesn't match that. Add a common-pc branch to sync them up. WARNING: .. do_patch: After meta data application, the kernel tree branch is standard/tiny/base.

[linux-yocto] [PATCH 6/6] intel-common: Have *-developer BSPs use standard/intel

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/intel branch for Intel platforms, so have intel-common/*-developer BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-core2-32-developer.scc | 2 ++ bsp/intel-common/intel-corei7-64-developer.scc | 2 ++ 2

[linux-yocto] [PATCH 5/6] intel-quark-tiny: Use standard/tiny/intel branch

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/tiny/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-quark-tiny.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[linux-yocto] [PATCH 3/6] common-pc*: Have *-standard BSPs use standard/intel

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/intel branch for Intel platforms, so have common-pc*/*-standard BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/common-pc-64/common-pc-64-standard.scc | 1 + bsp/common-pc/common-pc-standard.scc | 1 + 2 files changed,

[linux-yocto] [PATCH 5/5] intel-quark-tiny: Use standard/tiny/intel branch

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/tiny/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-quark-tiny.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[linux-yocto] [PATCH 1/6] intel: Use standard/intel branch

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-core2-32-standard.scc | 2 ++ bsp/intel-common/intel-corei7-64-standard.scc | 2 ++

[linux-yocto] [PATCH 0/6] linux-yocto-4.4: Use */intel branches

2016-05-24 Thread Tom Zanussi
In order to provide more timely support for Intel platforms, this patchset makes use of a set of dedicated */intel branches to be created for the linux-yocto 4.4 kernel. These branches and the corresponding kernel metadata branches provide a place to add Intel-specific features and updates which

[linux-yocto] [PATCH 3/5] common-pc*: Have *-standard BSPs use standard/intel

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/intel branch for Intel platforms, so have common-pc*/*-standard BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/common-pc-64/common-pc-64-standard.scc | 1 + bsp/common-pc/common-pc-standard.scc | 1 + 2 files changed,

[linux-yocto] [PATCH 2/5] intel: Use standard/preempt-rt/intel branch

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/preempt-rt/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-core2-32-preempt-rt.scc | 2 ++ bsp/intel-common/intel-corei7-64-preempt-rt.scc | 2

[linux-yocto] [PATCH 1/5] intel: Use standard/intel branch

2016-05-24 Thread Tom Zanussi
We now have a dedicated standard/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi --- bsp/intel-common/intel-core2-32-standard.scc | 2 ++ bsp/intel-common/intel-corei7-64-standard.scc | 2 ++

[linux-yocto] [PULL REQUEST] Broxton related backports for linux-yocto-4.4

2016-05-24 Thread California Sullivan
Hi Bruce, This is a set of backports from upstream. I have tested allyesconfig, allnoconfig, and standard builds and can't find anything wrong there. I have also tested running the kernel on MinnowBoard Max and there are no new errors or warnings. Let me know if I need to make any modifications

Re: [linux-yocto] usb: ehci: lockdep splat at startup

2016-05-24 Thread Bruce Ashfield
On 2016-05-24 3:05 AM, Zhenbo Gao wrote: Hi All, Ericsson AB found the following lockdep splat information on axxiaarm board: [ 4.491058] == [ 4.497232] [ INFO: possible circular locking dependency detected ] [ 4.503495] 4.1.15-rt13+ #8 Not

Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Randle, William C
On Mon, 2016-05-23 at 19:07 -0700, Graydon, Tracy wrote: > Fixed the path for the publishing of the eclipse plugins. They were > going to the wrong subdirectory under downloads. > > Signed-off-by: Graydon, Tracy > --- >  bin/release_scripts/release.py | 22

Re: [yocto] Retrieve SRCREV variable value outside of a specific recipe (not modifying it)

2016-05-24 Thread Christopher Larson
On Tue, May 24, 2016 at 7:32 AM, Michael Hu wrote: > Hi, > > My goal is to pull recipe's SRCREV variable into a top level *.bbclass > file. I understand we can use SRCREV_pn- to modify the > revision on the fly outside of recipe in configuration files but when I > print out

[yocto] Retrieve SRCREV variable value outside of a specific recipe (not modifying it)

2016-05-24 Thread Michael Hu
Hi, My goal is to pull recipe's SRCREV variable into a top level *.bbclass file. I understand we can use SRCREV_pn- to modify the revision on the fly outside of recipe in configuration files but when I print out SRCREV information using ${SRCREV_pn-recipename} all I got back is the recipe name

Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py

2016-05-24 Thread Flanagan, Elizabeth
pulled into master. thanks! -b On 24 May 2016 at 03:12, Graydon, Tracy wrote: > Remove the step for syncing the staged release to downloads directory. We > pretty much NEVER do the sync to downloads at the time we do staging. Sync > happens much later, as a separate

Re: [yocto] Change in override behavior?

2016-05-24 Thread Richard Purdie
On Fri, 2016-04-29 at 22:09 +1200, Paul Eggleton wrote: > On Fri, 29 Apr 2016 12:00:58 Gary Thomas wrote: > > On 2016-04-29 11:51, Paul Eggleton wrote: > > > On Fri, 29 Apr 2016 09:24:23 Gary Thomas wrote: > > > > On 2016-04-29 09:16, Paul Eggleton wrote: > > > > Indeed, my machine names do have

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

2016-05-24 Thread piotr.lewicki
So I understand that 1 and 2 should be applied and 3rd is already merged into master (of poky). I cannot wait to for your fixes for gst-omx and later omxplayer. Thanks, Piotr On 24.05.2016 14:06, Herve Jourdain wrote: Hi Piotr, Please make sure you have the latest series, the 02 was modified

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

2016-05-24 Thread piotr.lewicki
On 24.05.2016 12:42, Herve Jourdain wrote: Hi Piotr, Hi, There were issues with patches 02, 07 and 12. 02- due to different overlay naming (overlays/vc4-kms-v3d-overlay.dtb instead of overlays/vc4-kms-v3d.dtbo) and 07 and 12 due to bump of linux-raspberrypi from 4.4.8 to 4.4.9 (on master). I

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

2016-05-24 Thread Herve Jourdain
Hi Piotr, I know that the omxplayer would not build at this time, because VC4 and userland will conflict, and currently omxplayer depends on userland. I will check if it can be supported with VC4 driver enabled, but for the moment it's true I disabled it in my build. Regarding your patches: 1.

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

2016-05-24 Thread piotr.lewicki
I have tried these patches, but there were some hunks and errors during applying to current master revision (69840c0bbe03c2e61601e2377c8e2adc264e0478). Building 'rpi-hwup-image' passed, but while building 'rpi-test-image' (omxplayer recipe) I have noticed some errors due to missing files: -

[linux-yocto] [PATCH] usb ehci-ci13612: Enable HCD_BH mode in ci13612 since EHCI doesn't work without it anymore.

2016-05-24 Thread Zhenbo Gao
From: Fredrik Markstrom The non-HCD_BH mode has a AB-BA lock problem, but we wan't HCD_BH mode anyway since it performs better and all other ehci drivers uses it. It will cause the lockdep splat below: [4.240663]