[linux-yocto] [PATCH 3/3] [kernel-cache] smp: Separate smp into 32 and 64 bit versions to avoid kernel warnings

When selecting SMP, some dependencies are needed, in the case of a 32 bit build CONFIG_X86_BIGSMP=y is required, but adding that to a 64 bit build causes warnings to be shown since X86_BIGSMP requires X86_32 [n] itself, which can only be true for a 32 bit build. This patch creates a 64 bit

[linux-yocto] [PATCH 2/3] [kernel-cache] bsp/mohonpeak: smp gets added by default, remove unnecessary include

mohonpeak.scc and mohonpeak32.scc are based on x86.scc and x86_64.scc which already include smp.scc, so remove the unnecessary include. [YOCTO #11743] Signed-off-by: Alejandro Hernandez --- bsp/mohonpeak/mohonpeak.scc | 3 ---

[linux-yocto] [PATCH 1/3] [kernel-cache] bsp/rangeley: smp gets added by default, remove unnecessary include

rangeley.scc and rangeley32.scc are based on x86.scc and x86_64.scc which already include smp.scc, so remove the unnecessary include. [YOCTO #11743] Signed-off-by: Alejandro Hernandez --- bsp/rangeley/rangeley.scc | 3 --- bsp/rangeley/rangeley32.scc | 3

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

Hi Darcy, Thank you for the feedback. Actually, depending on what exactly you mean by user supplied script, this patch set for the concept already supports that. I'm not sure if my attachments got skewered by the mailing list or not but if you can see my patch

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

Hi, It would also be nice to add some sort of hook script support where user supplied hook script performs a check and returns either a "yes it's OK" or a "no have to rebuild it" status. And then tie that into the dependency logic. I have unusual use case where I need to have a dependency on

[yocto] QA cycle report for 2.1.3 rc2

Hello All, Here is the report for the 2.1.3 rc2 full point release test cycle. Full Report : https://wiki.yoctoproject.org/wiki/WW26_-_2017-30-06_-_Full_Pass_2.1.3_rc2 === Summary The QA cycle for release 2.1.3 rc2 is complete for this release cycle the testing team focused

[yocto] [ANNOUNCEMENT] Milestone 1 for Yocto Project 2.4 now available.

The first milestone release for Yocto Project 2.4 is available for download now. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.4_M1/ eclipse-poky-mars 92aa0e79e8b01c56f0670af3cd8296ec68b43350 eclipse-poky-neon 83e0083ef3a71e10039ace7d18057dddc154408b meta-qt3

[yocto] Yocto Project Status WW26’17 EOW

Current Dev Position: Preparing for YP 2.4 M2 Next Deadline: YP 2.4 M2 Cut off is July 17, 2017 SWAT team rotation: Stephano -> Maxin on June 30, 2017. SWAT team rotation: Maxin -> Cal on July 7, 2017. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·

[yocto] How to find out the rdepends of certain package

Hi, experts I'm facing following problem, when building a image. The following packages have unmet dependencies: openssh-dev : Depends: openssh (= 7.1p2-r0.0) but it is not going to be installed Recommends:

Re: [yocto] [meta-raspberrypi] How to add a own dts file and patch the dts makefile

Hi, On Fri, Jun 30, 2017 at 3:35 PM, wrote: > Hej > > It's friday and I have some time to play a bit around. I like to build a > simple test-adapter using a RPi. I want to connect some of the 40GPIO pins > with a custom mainboard. For that I like to define the pin

[yocto] [meta-raspberrypi] How to add a own dts file and patch the dts makefile

Hej It's friday and I have some time to play a bit around. I like to build a simple test-adapter using a RPi. I want to connect some of the 40GPIO pins with a custom mainboard. For that I like to define the pin behaviour by an own dts file. I created my own dts file (testboard.dts) + a simple

Re: [yocto] [meta-raspberrypi][PATCH] rpi-base: wic: generate entries for u-boot

On Thu, Jun 29, 2017 at 9:01 PM, Andrea Galbusera wrote: > This commit allow wic generated images to work when we want u-boot to > load the kernel image. > > Augment IMAGE_BOOT_FILES with the proper entries when KERNEL_IMAGETYPE > is "uImage". More specifically add u-boot image

[yocto] RFC: Backwards compatibility checking sstate-cache

Hi, at BMW Car IT we are working on an experimental feature to improve sstate cache hits and we are looking for comments on the approach who might have some insights to the problem and seeing if anyone is interested in the feature for mainline. The sstate-cache of a recipe is tied closely to its