[yocto] BSP layer for Firecracker: Launch point #linux #yocto

Hi, Following up on my earlier email; it seems that a BSP layer targeting the Firecracker VM model could/should pay some dividends. Recapping the Firecracker 'board' model is: "only 5 emulated devices are available: virtio-net, virtio-block, virtio-vsock, serial console, and a minimal keyboard

[linux-yocto] v5.2.x - stable updates comprising v5.2.39

Bruce, Yocto kernel folks: Here is the next 5.2.x stable update "extension" primarily created for the Yocto project, as the next v5.2.x post-EOL release. The content is from an audit of what went into the v5.4.19 to v5.4.21 releases - plus any upstream commits listed as Fixes: for backports in

[yocto] oddities(?) when appending to an override

in aid of torturing myself, i'm poring over the bitbake manual and i recall the initial confusion i had when reading the section on overrides and appends, especially section 3.3.3 which turns things around by showing what happens when applying an append to an override, as opposed to the other

Re: [yocto] [WIC] Multiple WKS Files

On 5/4/20 11:14 AM, Rudolf J Streif wrote: On 5/2/20 2:47 PM, Joshua Watt wrote: On Sat, May 2, 2020, 1:22 PM Rudolf J Streif mailto:rudolf.str...@ibeeto.com>> wrote: eMMC devices commonly have three hardware partitions: two boot partitions and a user partition. I was looking

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (5/5) Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto

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

All, YP M+ or high bugs which moved to a new milestone in WW18 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 13459 sdk: compiler targets glibc, even though rootfs uses musl-libc

[yocto] Enhancements/Bugs closed WW18!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.pur...@linuxfoundation.org 11 akuster...@gmail.com 2 alex.kana...@gmail.com 1 hongxu@windriver.com 1 alejan...@enedino.org 1 ee.peng.y...@intel.com 1 Grand Total 17

Re: [yocto] [WIC] Multiple WKS Files

On 5/2/20 2:47 PM, Joshua Watt wrote: > > > On Sat, May 2, 2020, 1:22 PM Rudolf J Streif > wrote: > > eMMC devices commonly have three hardware partitions: two boot > partitions and a user partition. I was looking for a convenient way to > have wic

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

All, Below is the list as of top 50 bug owners as of the end of WW18 of who have open medium or higher bugs and enhancements against YP 3.2. There are 125 possible work days left until the final release candidates for YP 3.2 needs to be released. Who Count

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [yocto] [error-report-web][PATCH] Add SPDX license headers to source files

On 2020-05-01 2:54 a.m., Milan Shah wrote: Hi All, This is Gentle Reminder to review these changes. This address bug #13530 https://bugzilla.yoctoproject.org/show_bug.cgi?id=13530 Patch to review: https://patchwork.openembedded.org/patch/170541/ Thanks Milan. Looks good to me. Michael,

Re: [yocto] #yocto do_package error for custom app

On Mon, 4 May 2020 at 14:06, Bastien0530 wrote: > I have just resolved the issue, that was a mistake in my makefile, I fixed > CC=GCC instead of CC?=GCC. FWIW, you never need that in a Makefile, as there is a default value for CC. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages

Re: [yocto] #yocto do_package error for custom app

Salut Bastien, On Mon, May 04, 2020 at 06:05:19AM -0700, Bastien0530 wrote: > This file is supposed to be my application. The `file` command on Linux (could be run on the host and not the target) will give you important info such as the architecture for which it was built. In that case, we would

[yocto] Building cython based module with numpy dependency in SDK

Hello! I've been trying to build a python package which has a component written in c that is used through cython. But when I try to build in the SDK I first got: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." I figured it had to do with

Re: [yocto] #yocto do_package error for custom app

This file is supposed to be my application. I tried to run it on my target cible but doesn't work. I have just resolved the issue, that was a mistake in my makefile, I fixed CC=GCC instead of CC?=GCC. Thanks for you answer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

[yocto] Yocto img file deployment

Hi, I have a yocto image: image.img. On my build PC I have > file image.img image.img: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,1), end-CHS (0x3ff,254,63), startsector 1, 802815 sectors, extended partition table (last) > fdisk -l image.img Disk image.img: 392 MiB, 411041792

Re: [yocto] BSP layer for Firecracker: Sensible? Advisable? #linux #yocto

On Mon, 4 May 2020 at 06:25, wrote: > A goal will be to squeeze out maximum performance and/or minimum-size. so I'm > wondering would a BSP layer deliver any benefit? The Firecracker VM has a > very small device list, with support for Intel x86_64 and ARM64 CPU's. The > devices are: "only 5

Re: [yocto] #yocto do_package error for custom app

On Mon, 4 May 2020 at 09:16, Bastien0530 wrote: > Subprocess > output:arm-poky-linux-gnueabi-objcopy:/home/galletpb/Documents/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/si4688-app/1.0-r0/package/usr/bin/si4688-app: > file format not recognized Please run 'file

[yocto] #yocto do_package error for custom app

Hi, I'm currently trying to add a cutsom app to my cutsom image for raspi3 and I encountered a problem during the do_package phase of the build of the image. ERROR: si4688-app-1.0-r0 do_package: Fatal errors occurred in subprocesses: Command '['arm-poky-linux-gnueabi-objcopy',