Re: [yocto] [meta-rockchip][PATCH 2/2] Add tinker-board-s machine configuration

On Mon 2020-02-10 @ 06:25:23 PM, Sergey Bostandzhyan wrote: > From: Sergey 'Jin' Bostandzhyan > > Asus Tinker Board-S has emmc on mmcblk1, this is also the default > configuration when building the image. If you need an image for booting > from the sd card set RK_BOOT_DEVICE to mmcblk0 > > Signe

Re: [yocto] [meta-rockchip][PATCH 1/2] Add configuration parameter to set boot device for the image

On Mon 2020-02-10 @ 06:25:22 PM, Sergey Bostandzhyan wrote: > From: Sergey 'Jin' Bostandzhyan > > wic modifies /etc/fstab on the root file system during image generation, > without the --ondisk parameter it assumes some default device name which > leads to an /etc/fstab file populated with /dev/s

[yocto] [meta-rockchip][PATCH 1/2] Add configuration parameter to set boot device for the image

From: Sergey 'Jin' Bostandzhyan wic modifies /etc/fstab on the root file system during image generation, without the --ondisk parameter it assumes some default device name which leads to an /etc/fstab file populated with /dev/sda entries. This is not correct for the machines in the rockchip layer

[yocto] [meta-rockchip][PATCH 2/2] Add tinker-board-s machine configuration

From: Sergey 'Jin' Bostandzhyan Asus Tinker Board-S has emmc on mmcblk1, this is also the default configuration when building the image. If you need an image for booting from the sd card set RK_BOOT_DEVICE to mmcblk0 Signed-off-by: Sergey Bostandzhyan --- README | 1

Re: [yocto] more nitpicky pedantry: question about DEFAULT_PREFERENCE

On Mon, 10 Feb 2020, Richard Purdie wrote: > On Sat, 2020-02-08 at 13:48 -0500, rpj...@crashcourse.ca wrote: > > On Sat, 8 Feb 2020, rpj...@crashcourse.ca wrote: > > ... snip ... > > > which seems odd as there don't appear to be any other recipes that > > > provide pkgconfig, and AIUI, the default

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

All, YP M+ or high bugs which moved to a new milestone in WW06 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 13332 AB fails if a new branch is built for the first time when it wants to compa

[yocto] Enhancements/Bugs closed WW06!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.pur...@linuxfoundation.org 14 akuster...@gmail.com 3 akus...@mvista.com 3 r...@burtonini.com 2 jpewhac...@gmail.com 2 randy.macl...@windriver.com 1 alex.kana...@gmail.com 1

[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: https://wiki.yoctoproject.org/wiki/Bug_Triage#N

[yocto] Current Top developers on Yocto Project 3.1

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

Re: [yocto] more nitpicky pedantry: question about DEFAULT_PREFERENCE

On Mon, 10 Feb 2020, Richard Purdie wrote: > On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote: > >consider under recipes-devtools the two directories "pkgconfig" > > and "pkgconf", and the respective .bb files: > > > > - pkgconfig_git.bb > > - pkgconf_1.6.3.bb > > > > the pk

[yocto] Unable to run bitbake core-image-minimal -c populate_sdk in poke "Warrior" branch.

I created a build environment for powerpc-nf using poke "warrior" branch. I was able to run "bitbake core-image-minimal" successfully. I was also able to run "bitbake core-image-minimal -c populate_sdk" successfully. Then I added a new package from my internal team. After adding this package, I w

Re: [yocto] more nitpicky pedantry: question about DEFAULT_PREFERENCE

On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote: > (part of the nitpickiness of some of these questions stems from > that, in my updated courseware, i want to use actual examples out of, > say, the openembedded layer, and not just contrived examples > involving > packages like "foo

Re: [yocto] more nitpicky pedantry: question about DEFAULT_PREFERENCE

On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote: > (part of the nitpickiness of some of these questions stems from > that, in my updated courseware, i want to use actual examples out of, > say, the openembedded layer, and not just contrived examples > involving > packages like "foo

Re: [yocto] more nitpicky pedantry: question about DEFAULT_PREFERENCE

On Sat, 2020-02-08 at 13:48 -0500, rpj...@crashcourse.ca wrote: > On Sat, 8 Feb 2020, rpj...@crashcourse.ca wrote: > ... snip ... > > which seems odd as there don't appear to be any other recipes that > > provide pkgconfig, and AIUI, the default provider for any recipe is > > the recipe with *exact

Re: [EXTERNAL] Re: [yocto] Clarifying install vs deploy

On Mon, Feb 10, 2020 at 11:22 AM Nicolas Dechesne wrote: > you use do_install() to install any content that you need to be added to your > rootfs/image, as you said. the content of $D will end up in a binary package > (rpm, deb, or ipk), and that package might eventually be installed into an >

Re: [yocto] Clarifying install vs deploy

On Mon, Feb 10, 2020 at 11:08 AM Oliver Westermann wrote: > > I was asked by a colleague for the difference between do_deploy and > do_install, which I both used mostly by checking similar recipes and copying > their methods, but now I'm having some questions as well. The Yocto dev > manual doe

Re: [yocto] Busybox and scripts licensing

On 05/02/2020 15:57, Ross Burton wrote: On Wed, 5 Feb 2020 at 12:16, wrote: Let's assume we have busybox on our device (that's populated by default by Yocto). What license shall be chosen for package containing custom shell scripts? I heard opinion, that all shell scripts running on Busybox s

[yocto] Clarifying install vs deploy

I was asked by a colleague for the difference between do_deploy and do_install, which I both used mostly by checking similar recipes and copying their methods, but now I'm having some questions as well. The Yocto dev manual doesn't list deploy at all, so my assumption is that why do_install is t

[yocto] [HELP] Create a new image recipe based on a (changed) existing one #yocto

Hi, I'm trying to create an image recipe based on an existing one. I've searched online, and I could find such an example. My problem is that the image I what to serve as a base is changed in another layer and I want to include those changes. Ex: (tree) Prj_root -> layer1 -> recipes-core -> im

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

Hi Stephen, The link in your email points to the 2019 minutes, I think the current link is https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit. Thanks, Paul On Mon, 3 Feb 2020 at 17:37, wrote: > > All, > > > > Just a reminder we will hold the monthly Yocto Proj