[linux-yocto] [yocto-5.8][PATCH 2/3] features/inline: remove

Remove CONFIG_OPTIMIZE_INLINING and associated features entirely. The config has been removed starting 5.7. https://github.com/torvalds/linux/commit/889b3c1245de48ed0cacf7aebb25c489d3e4a3e9 Signed-off-by: Anuj Mittal --- bsp/intel-common/intel-common-drivers.scc | 1 -

[linux-yocto] [yocto-5.8][PATCH 1/3] intel-tco: switch ITCO_WDT to loadable module

The watchdog driver can't be y when MFD driver is a loadable module. Switch the config from y to m to avoid cases when MFD driver is also enabled as m. See: https://github.com/torvalds/linux/commit/b30c1a464c29baf646a5726d90ea3537e775ac85 Signed-off-by: Anuj Mittal ---

[linux-yocto] [yocto-5.8][PATCH 3/3] features: rename INTEL_PMC_IPC to MFD_INTEL_PMC_BXT

And set it to m to avoid conflicts when coretemp.scc is also included. Also fix the dependencies that rely on this config. See: https://github.com/torvalds/linux/commit/25f1ca31e230598eaf3c38d387a355a64bd772a7 Signed-off-by: Anuj Mittal --- features/soc/broxton/broxton.cfg | 2 +-

Re: [yocto] ABI Version for MIPS platform changed from 0 to 5

On Mon, Aug 24, 2020 at 7:13 AM MikeB wrote: > > Your solution worked great! Thank you for that as I don't think I would have > tracked that down soon. > > I now have a follow on problem that I have not been able to solve yet - > mostly because my knowledge of the GNU toolchain is not very

Re: [linux-yocto] [yocto-5.4][master][PATCH] features/media: set default for DVB_CORE to m

On Fri, Aug 21, 2020 at 2:03 AM Lee, Chee Yang wrote: > Request to merge this patch to 4.19 too. > Cherry picked and pushed. Bruce > > Thanks > > > > *From:* linux-yocto@lists.yoctoproject.org < > linux-yocto@lists.yoctoproject.org> *On Behalf Of *Bruce Ashfield > *Sent:* Saturday, 8

Re: [yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

On Mon, Aug 24, 2020 at 12:50 PM Monsees, Steven C (US) via lists.yoctoproject.org wrote: > > > > I am having trouble configuring my SDK to use the meta-clang compiler-rt > component properly. > > > > How do I configure my build so meta-clang brings in compiler-rt and generates > the

[yocto] M+ & H bugs with Milestone Movements WW34

All, YP M+ or high bugs which moved to a new milestone in WW34 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 6437 Document how to set up the Yocto Project for production work

[yocto] Current high bug count owners for Yocto Project 3.2

All, Below is the list as of top 46 bug owners as of the end of WW34 of who have open medium or higher bugs and enhancements against YP 3.2. There are 47 possible work days left until the final release candidates for YP 3.2 needs to be released. Who Count richard.pur...@linuxfoundation.org

[yocto] #sdk -Standard SDK build with cmake and meta-clang gives error when I attempt topull in compiler-rt

I am having trouble configuring my SDK to use the meta-clang compiler-rt component properly. How do I configure my build so meta-clang brings in compiler-rt and generates the libclang_rt.binutils-x86_64.a library I require? When I attempt to build in "compiler-rt" component I get the CMAKE

[yocto] [meta-security][dunfel][PATCH] trousers: Several Security fixes

From: Armin Kuster Source: meta-security MR: 105088 Type: Security Fix Disposition: Backport from http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/commit/?id=787ba6faeaa8823a4d87e5edd15581cb4e12fa70 ChangeID: b55bccb002b9eb2c49dfe380406e2597bb1ade90 Description: Fixes: CVE-2020-24332

Re: [yocto] Yocto standard SDK/cmake/ and meta-clang build issue

Mikko: I understand, had to read through it twice... I do not think this is my issues, target and host both x86_64 based... Thanks, Steve -Original Message- From: Monsees, Steven C (US) Sent: Monday, August 24, 2020 1:24 PM To: 'mikko.rap...@bmw.de' Cc: yocto@lists.yoctoproject.org

Re: [yocto] Additional log handler

Thanks to both of you - seems like I missed out on BB_LOGCONFIG, but it's exactly what I was looking for. Regards Konrad On 24.08.20 15:59, Joshua Watt wrote: On 8/24/20 8:26 AM, Richard Purdie wrote: On Mon, 2020-08-24 at 08:10 -0500, Joshua Watt wrote: The newer log handling uses Python's

Re: [yocto] Yocto standard SDK/cmake/ and meta-clang build issue

Mikko: I am x86_64 intel based, are you saying I have to add " clang-cross-canadian" for my platform ?, Also, "clang-cross bit" ?, not sure I follow, can you elaborate ? Thanks, Steve -Original Message- From: mikko.rap...@bmw.de [mailto:mikko.rap...@bmw.de] Sent: Monday, August 24,

Re: [yocto] Yocto standard SDK/cmake/ and meta-clang build issue

Hi, On Mon, Aug 24, 2020 at 02:38:54PM +, Monsees, Steven C (US) via lists.yoctoproject.org wrote: > > I am having trouble with configuring my SDK for meta-clang... > > When I build my SDK, I setup the following: > > SDKMACHINE = "x86_64" > SDKIMAGE_FEATURES_append = " staticdev-pkgs" >

Re: [yocto] ABI Version for MIPS platform changed from 0 to 5

Your solution worked great! Thank you for that as I don't think I would have tracked that down soon. I now have a follow on problem that I have not been able to solve yet - mostly because my knowledge of the GNU toolchain is not very deep. This problem only shows up in my Dunfell MIPS build - I

Re: [yocto] Additional log handler

On 8/24/20 8:26 AM, Richard Purdie wrote: On Mon, 2020-08-24 at 08:10 -0500, Joshua Watt wrote: The newer log handling uses Python's structure logging configuration [1], so you should be able to use whatever capabilities it has (including logging different domains/levels to a separate file).

Re: [yocto] Additional log handler

On 8/24/20 3:53 AM, Richard Purdie wrote: On Sun, 2020-08-23 at 17:01 +0200, Konrad Weihmann wrote: Hi all, when running bitbake in CI I would like to add an additional log handler to used python logging to catch *ALL* (task warnings, dangling append, qa issues, a.s.o.), instead of manually

Re: [yocto] Additional log handler

On Mon, 2020-08-24 at 08:10 -0500, Joshua Watt wrote: > The newer log handling uses Python's structure logging configuration > [1], so you should be able to use whatever capabilities it has > (including logging different domains/levels to a separate file). In > fact, this is the only way logging

Re: [yocto] [PATCH 0/3] yocto-bsp/poky: kernel updates and default

On Sun, Aug 23, 2020 at 11:23 PM Mittal, Anuj wrote: > Hi Bruce, > > On Fri, 2020-08-21 at 15:07 -0400, Bruce Ashfield wrote: > > From: Bruce Ashfield > > > > Richard, > > > > Similar to oe-core, these are the patches I'm carrying to update the > > reference BSPs to the latest 5.4 (we still

Re: [yocto] Yocto uses older PV instead of newest - how to figure out why?

Hi Oliver, On August 24, 2020 2:02:26 PM GMT+02:00, Oliver Westermann wrote: >Hey, > >we're porting our yocto from an older NXP iMX release to their newest >BSP, upgrading yocto in the process from sumo to zeus. >Using their current setup, the layers provide one recipe in two >versions - 0.2

Re: [yocto] Yocto uses older PV instead of newest - how to figure out why?

Quoting Oliver Westermann : Hey, we're porting our yocto from an older NXP iMX release to their newest BSP, upgrading yocto in the process from sumo to zeus. Using their current setup, the layers provide one recipe in two versions - 0.2 and 1.0. imx-boot to be precise. I assumed yocto

[yocto] Yocto uses older PV instead of newest - how to figure out why?

Hey, we're porting our yocto from an older NXP iMX release to their newest BSP, upgrading yocto in the process from sumo to zeus. Using their current setup, the layers provide one recipe in two versions - 0.2 and 1.0. imx-boot to be precise. I assumed yocto would use the newer version, but it

Re: [yocto] Additional log handler

On Sun, 2020-08-23 at 17:01 +0200, Konrad Weihmann wrote: > Hi all, > > when running bitbake in CI I would like to add an additional log > handler to used python logging to catch *ALL* (task warnings, > dangling append, qa issues, a.s.o.), instead of manually grepping > through the console log.

Re: [yocto] Additional log handler

Hi Konrad, Every task has a log file in their correspondent recipe workdir that normally it is indicated by yocto when a recipe fails in the error message. Anyway you always can redirect the bitbake output to file with linux pipes. By this way: bitbake > file.txt You can find more