Thursday, 2021-09-16

*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto00:07
*** xmn <xmn!> has joined #yocto00:12
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)00:13
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto00:24
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)00:30
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto00:46
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)00:51
*** fray <fray!~fray@> has quit IRC (Ping timeout: 268 seconds)01:01
*** fray <fray!~fray@> has joined #yocto01:03
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto01:05
*** sakoman <sakoman!~steve@> has quit IRC (Read error: Connection reset by peer)01:09
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)01:10
*** sakoman <sakoman!> has joined #yocto01:25
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto01:36
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)01:41
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto02:04
*** fray <fray!~fray@> has quit IRC (Ping timeout: 252 seconds)02:05
*** Ad0 <Ad0!~Ad0@> has quit IRC (Ping timeout: 260 seconds)02:06
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)02:09
*** Ad0 <Ad0!~Ad0@> has joined #yocto02:11
*** fray <fray!~fray@> has joined #yocto02:19
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)02:43
*** amitk <amitk!~amit@> has joined #yocto04:11
*** zeddii <zeddii!> has quit IRC (Ping timeout: 260 seconds)04:28
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto05:11
*** fitzsim <fitzsim!> has quit IRC (Ping timeout: 250 seconds)05:28
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto05:37
*** zeddii <zeddii!> has joined #yocto05:52
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:13
JosefHolzmayr[m]yo dudX06:21
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Quit: WeeChat 3.1)06:30
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: Textual IRC Client:
*** frieder <frieder!> has joined #yocto06:33
*** mckoan|away is now known as mckoan06:35
mckoangood morning06:35
*** ThomasD13 <ThomasD13!> has joined #yocto06:35
*** tre <tre!> has joined #yocto06:35
*** frieder <frieder!> has quit IRC (Ping timeout: 265 seconds)06:39
mckoanJosefHolzmayr[m]: how was the webinar yesterday?06:40
JosefHolzmayr[m]mckoan: i think it was a real success :)06:41
JosefHolzmayr[m]the video is even up on youtube already, but I'lll probably not promote it until tomorrow or such.06:41
mckoanJosefHolzmayr[m]: great! Congrates.06:43
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:52
*** frieder <frieder!> has joined #yocto06:52
*** zpfvo <zpfvo!~fvo@> has joined #yocto06:54
coldspark29[m]Does anyone know how solve this?... (full message at
coldspark29[m]I am pretty new to Yocto and am hoping that I can find some initial assistance here06:57
JosefHolzmayr[m]if i had to guess then i'd say that this is a bug in the recipe.06:58
coldspark29[m]Yeah and unfortunately NXP doesn't provide support for Chromium06:59
JosefHolzmayr[m](because, this is what the message actually suggests - and sorry, building the combination of browser + graphics stack + acceleration is not exactly a beginner level problem)06:59
coldspark29[m]Hmm the weird thing is that it builds fine for the i.MX8, but this is the i.MX607:00
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto07:01
JosefHolzmayr[m]then you'll have to dig into the machine configurarations, and find out what the one machine sets/enables that the other doesn't. if i had to guess again, then the libdrm provider is filtering on compatible machines. or something similar.07:03
coldspark29[m]Okay thanks will have a look at them07:06
*** rfuentess <rfuentess!~rfuentess@2a01:598:88b1:1122:8db6:b968:2b79:5a19> has joined #yocto07:10
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)07:19
*** Belsirk <Belsirk!~rfuentess@2a01:598:b028:f364:8db6:b968:2b79:5a19> has joined #yocto07:30
*** rfuentess <rfuentess!~rfuentess@2a01:598:88b1:1122:8db6:b968:2b79:5a19> has quit IRC (Ping timeout: 240 seconds)07:34
*** fray <fray!~fray@> has quit IRC (Ping timeout: 268 seconds)07:34
*** prabhakarlad <prabhakarlad!> has joined #yocto07:38
*** fbre <fbre!~fbre@> has joined #yocto07:38
*** Tyaku <Tyaku!> has joined #yocto07:44
*** fray <fray!~fray@> has joined #yocto07:47
*** Tyaku <Tyaku!> has quit IRC (Client Quit)07:47
*** camus1 <camus1!~Instantbi@> has joined #yocto07:56
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 252 seconds)07:59
*** camus1 is now known as camus07:59
*** camus <camus!~Instantbi@> has quit IRC (Read error: Connection reset by peer)08:06
*** camus1 <camus1!~Instantbi@> has joined #yocto08:06
*** camus1 is now known as camus08:09
*** camus1 <camus1!> has joined #yocto08:13
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 252 seconds)08:15
*** camus1 is now known as camus08:15
*** camus <camus!> has quit IRC (Read error: Connection reset by peer)08:18
*** camus <camus!~Instantbi@> has joined #yocto08:23
*** kayterina <kayterina!> has joined #yocto08:38
*** Tyaku <Tyaku!> has joined #yocto08:39
coldspark29[m]How to you actually run ``bitbake-layers`` etc? Is it discouraged to put the binaries in ``/usr/bin``, because I find it a bit tedious to always specify the whole path ``poky/bitbake/bitbake-layers`` to inspect the layers08:42
qschulzcoldspark29[m]: if you source the poky oe-init-buildenv sdcript, it's part of your PATH and you can call it directly08:45
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)08:45
coldspark29[m]qschulz: But just as long as I keep that shell window open I assume?08:45
coldspark29[m]Ah I might have moved that poky foldet08:46
qschulzcoldspark29[m]: yes, the source applies only to the current shell08:46
coldspark29[m]Yeah but it doesn't work. Maybe because I use zsh08:47
qschulzi use zsh08:48
qschulzso maybe you can tell us what you're doing and what's the error you're seeing?08:48
*** florian <florian!> has joined #yocto08:48
coldspark29[m]I just called ``oe-init-build-env`` and it doesn't find bitbake08:49
qschulzbecause you're supposed to source the script not call it08:49
coldspark29[m]Ah right08:49
*** Tyaku <Tyaku!> has joined #yocto08:49
*** Tyaku <Tyaku!> has quit IRC (Client Quit)08:50
*** Tyaku <Tyaku!> has joined #yocto08:50
coldspark29[m]Now it finds it. If I do this in an already set up build environment, will it overwrite the buld folder?08:51
coldspark29[m]I also use custom buidl folder names08:51
qschulzpass your BUILDDIR directory as an argument to oe-init-build-env and it'll set it up correctly08:51
qschulzit'll not overwrite whatever you already have08:52
coldspark29[m]Okay, so I have to source the file every time I open a new shell. Thanks08:52
qschulzwell, if you want to build from that shell08:53
qschulzor use bitbake tools08:53
coldspark29[m]But why not install bitbake globally?08:53
coldspark29[m]There must be a good reason08:53
qschulzbecause bitbake version is fixed for a given release of openembedded-core and other layers08:54
qschulzso if you have multiple builds each from different yocto/oe-core versions, you effectively have different bitbake too08:54
coldspark29[m]Thought so08:55
qschulzalso... you could run a bitbake from multiple different projects (different repos and layers) at the same time, which is not possible from the same bitbake08:55
qschulzbecause it's setting up a lock to avoid concurrent use of bitbake for the same project08:55
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)08:57
coldspark29[m]Yeah Yocto can get messy. I see that08:59
*** Guest69 <Guest69!~Guest69@> has joined #yocto09:00
qschulzbitbake is not allowing concurrent use of itself specifically so that Yocto cannot get messy ;)09:05
*** Tyaku <Tyaku!> has joined #yocto09:16
*** BCMM <BCMM!~BCMM@user/bcmm> has joined #yocto09:17
RPJaMa: there is a patch in master-next which attempts to fix the task accounting for the UI. Not well tested yet but testing welcome09:34
RPrburton: ^^^09:34
fbreHi, if I have a .wic file in my RAM disk, how can I write it to partition? Can I use the tool dd to write the image? 7zip sees two files in the .wic file, 0.fat and 1.img09:38
fbre(As I have a running yocto, I want to overwrite the boot and root partition with a newer yocto build)09:41
fbre... I mean a running yocto should overwrite its own boot and root partition09:43
*** pabigot <pabigot!> has quit IRC (Ping timeout: 245 seconds)09:50
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto09:51
*** pabigot <pabigot!> has joined #yocto09:51
JosefHolzmayr[m]are there prebuilt (e)sdks for poky releases somewhere?09:55
fbreSeems, dd if=/tmp/1.img of=/dev/mmcblk1p2 bs=512 count=698982    could do the job but I'm not sure09:56
JosefHolzmayr[m]fbre: leave out the count and just dd, usually. but in most cases you don't want to target the partition, rather go for the whole nand device.09:59
JosefHolzmayr[m]yet, this is something that the documentation for your hw should cover.09:59
fbreJosefHolzmayr[m] thanx!10:00
*** eduardas <eduardas!~eduardas@> has joined #yocto10:00
fbreJosefHolzmayr[m] not sure what you mean with sdk.10:03
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)10:04
*** Guest69 <Guest69!~Guest69@> has quit IRC (Ping timeout: 256 seconds)10:04
fbreJosefHolzmayr[m] Do you want to develop user space apps based on yocto and you're looking for a toolchain?10:04
*** Tyaku <Tyaku!> has joined #yocto10:10
*** fbre <fbre!~fbre@> has quit IRC (Quit: Client closed)10:10
*** fbre <fbre!~fbre@> has joined #yocto10:11
JosefHolzmayr[m]fbre: Not exactly, but close enough, yes.10:17
*** Tyaku <Tyaku!> has quit IRC (Quit: Lost terminal)10:24
*** zkrx <zkrx!~slimshady@> has joined #yocto10:25
fbreJosefHolzmayr[m] Does help?10:28
*** zkrx <zkrx!~slimshady@> has quit IRC (Quit: zkrx)10:32
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:32
*** zkrx <zkrx!~slimshady@> has joined #yocto10:33
*** Guest69 <Guest69!~Guest69@> has joined #yocto10:34
*** mckoan is now known as mckoan|away10:34
JosefHolzmayr[m]fbre: unfortunately that doesn't work for my use case. But thanks, good idea.10:38
*** eduardas <eduardas!~eduardas@> has quit IRC (Remote host closed the connection)10:41
*** eduardas <eduardas!~eduardas@> has joined #yocto10:42
rburtonJosefHolzmayr[m]: -toolchain- is populate_sdk, -toolchain-ext- is populate_sdk_ext.  iirc, the esdks are they're build as minimal so they need to download the sstate to be usable (instead of being 3GB tarballs)10:43
*** Guest69 <Guest69!~Guest69@> has quit IRC (Quit: Client closed)10:44
JosefHolzmayr[m]rburton okay thanks, will check it out.10:48
JosefHolzmayr[m]-minimal is perfectly enough.10:49
*** willo <willo!> has quit IRC (Ping timeout: 260 seconds)10:49
*** willo <willo!> has joined #yocto10:51
*** xmn <xmn!> has quit IRC (Read error: Connection reset by peer)11:06
*** xmn <xmn!> has joined #yocto11:07
coldspark29[m]Is there any way to speed up the chromium build? It takes up to 4 hours on my machine11:10
JosefHolzmayr[m]coldspark29 to some extent: get faster storage, get more CPUs. Besides that: nope. Chromium is just hide.11:12
*** yates <yates!> has quit IRC (Remote host closed the connection)11:13
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)11:13
coldspark29[m]Yeah it's awful. I am trying to find the misconfiguration of the recipe and I have to wait for hours after every try11:13
coldspark29[m]I need a Threadripper hahahaha11:14
JaMait takes around an hour on threadripper-3970x-128gb11:14
JaMasee if you want to compare your machine with others11:15
fbreI can extract a .wic file easily with 7zip. How can I extract it without 7zip in a Linux commandline shell?11:22
rburtondepends on the wic11:23
rburtontypically, they're not compressed11:23
fbregunzip and tar -xvzf  failed11:23
rburtonwhat does `file` say the wic actually is11:23
qschulzfbre: why do you want to extract the wic?11:23
*** prabhakarlad <prabhakarlad!> has joined #yocto11:23
rburtonnormally you'd loopback mount it, as its a file system11:24
rburtonfile core-image-base-fvp-base.wic                                                                                                                                                                                                                                                                                   core-image-base-fvp-base.wic: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x10,0,1), end-CHS (0x3ff,3,32), startsector 2048, 37271611:25
fbreI have a running user app on my device which receives the .wic file via webinterface. I put it in the RAM disk /tmp and want to extract it. Then I want to do: dd if=/tmp/0.fat of=/dev/mmcblk1p1 bs=512  and  dd if=/tmp/1.img of=/dev/mmcblk1p2 bs=51211:26
rburtonbut a wic file isn't an archive11:27
rburtonif you're sending a file system that gets written directly to disk, i'd be sending something with checksums11:27
fbreThis is to exchange the boot and root partition11:27
rburton(sounds like you're reinventing swupdate fwiw)11:28
rburtonbut basically, a typical wic is a disk image.  you can't just extract the file systems unless you're root and loopback mount it.  make a new artifact which is the partitions in an archive.11:29
fbreok, making a new artifact seems to be a good idea. And yes, it must be secured with checksums or ssl signing11:30
fbreI'm curious about swupdate fwiw now. I must find out what that is11:30
fbreI was just wondering because 7zip.exe can extract a .wic file11:31
qschulzfbre: you have plenty of update SW11:31
qschulzrauc,, swupdate, are the ones that comes to my mind right now11:31
rburtonfbre: 7zip web site says it can browse disk images11:32
rburtonwhich is why it works11:32
rburtonon linux, just loopback or fuse mount11:32
fbreUsually, I update my user apps and system libs via opkg. This way I install into my current layer of the running overlayfs (which is in partition 3 and 4). But rarely I have the situation to exchange the base system as well, and this is partition 1 and 211:34
fbreFor the base system, I thought writing the .wic file to flash is a good idea. It just contains the lower layer of the overlayfs (with just the root filesystem of a naked yocto Linux) without the actual firmware11:36
*** kayterina <kayterina!> has quit IRC (Quit: Leaving)11:36
fbreopkg can't read disk images, right?11:38
coldspark29[m]<JosefHolzmayr[m]> "coldspark29 to some extent..." <- You think Firefox builds faster?11:43
coldspark29[m]Or have you tried ^^11:43
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 265 seconds)11:48
JosefHolzmayr[m]coldspark29 I haven't tried. I just can rightfully state that they are huge when compared to most other applications we see in the yocto ecosystem.11:49
*** jwillikers <jwillikers!> has joined #yocto11:57
*** xmn <xmn!> has quit IRC (Ping timeout: 265 seconds)11:59
*** warthog9 <warthog9!> has quit IRC (Quit: Leaving)12:02
*** Belsirk is now known as rfuentess12:05
fbreNow I've bitbaked a bmap-tools ipk file. Is it a good idea to extract the disk image with bmap-tools?12:10
fbreor maybe even write the .wic file using bmaptool12:10
*** warthog9 <warthog9!> has joined #yocto12:11
smurrayfbre: it'll be a lot faster to write with bmaptool, that's the point12:11
fbreI'm find that example of "sudo bmaptool copy dev-image-20190528085324.rootfs.wic.gz /dev/sdX" in the internet which seems so as if one can write a .wic file to flash.12:12
fbreBut I wonder if I can write ONLY partition 1 and 2 and do not delete my partition 3 and 412:13
fbreMaybe I have to play around with that tool and trial and error what happens12:14
qschulzfbre: create a wic file with only partition 1 and 212:14
qschulzbut honestly, just use a SW updater12:14
*** Guest8 <Guest8!~Guest8@> has joined #yocto12:15
smurrayfbre: it might be possible to modify the .bmap file to skip some ranges, but that'd take some hacking on your part12:15
fbreqschulz: my .wic file just contains partition 1 and 2. But I'm not sure if bmaptool destroys 3 and 412:15
Guest8for some reason my virtual/kernel (linux-raspberrypi) and my external modules (using inherit module) have different kernel versions specified in them (4.19.93 SMP preempt mod_unload modversions aarch64 vs 4.19.93). any idea how i can go about trying to resolve this?12:16
smurrayfbre: bmaptool will only write out blocks with data, so maybe not, but it's possible it'd nuke your partition table if the new image only has 2 partitions12:18
fbresmurray: (y)12:19
smurrayfbre: but as qschulz says, most people use a updater in products, e.g. swupdate, rauc, Mendor, etc.12:19
fbreHmm, at the moment I cannot realize how those updaters logically assign in my known world of tools '=D  I just know dd, bmaptool and opkg12:21
fbreIs it a third tools category for putting software in flash?12:23
smurrayyeah, google swupdate or rauc, they have good documentation on what they do12:23
fbrehmm jep12:33
jonmason should be accessible, right?12:45
jonmasonI'm getting forbidden12:45
fbregrmpf... bitbake python3-pkg-resources    leads to     ERROR: Nothing provides 'python3-pkg-resources'.    But it's needed by python3-setuptools    and this is needed by bmap-tools12:46
qschulzfbre: are you sure python3-pkg-resources isn't a package built by a recipe?>12:46
qschulzjonmason: I don't think I've ever had access to the directory from a browser12:47
qschulzif you give it a full path that Yocto would be requested I guess it'll work?12:47
fbreqschulz ah OK, I've found it in tmp/deploy/ipk/aarch6412:50
fbreSeems bitbaking python3-setuptools have build it as well12:51
jonmasonqschulz: I added it to my local.conf and build times appear to be the same without it being present (at ~30 mins for qemuarm)12:51
jonmasonI was hoping that it was just a permission problem12:51
*** rfuentess <rfuentess!~rfuentess@2a01:598:b028:f364:8db6:b968:2b79:5a19> has quit IRC (Remote host closed the connection)12:52
qschulzjonmason: are you building a machine that is available in the sstate-mirror and using uninative?12:52
*** rfuentess <rfuentess!~rfuentess@2a01:598:b028:f364:8db6:b968:2b79:5a19> has joined #yocto12:52
qschulzalso, I think there's something related to hashserv12:52
qschulzjonmason: c.f.
jonmasonqschulz: thanks, i'll mess with that12:56
*** Guest8 <Guest8!~Guest8@> has quit IRC (Quit: Client closed)12:57
fbrebmaptool: ERROR: cannot open block device '/dev/mmcblk1' in exclusive mode: [Errno 16] Device or resource busy: '/dev/mmcblk1'12:59
fbrehmmm bmaptool is installed now but it refuses to work with that error12:59
fbrebmaptool copy /tmp/core-image-minimal-imx8mmevk.wic.gz /dev/mmcblk113:00
*** Belsirk <Belsirk!~rfuentess@2a01:598:88b1:1122:8db6:b968:2b79:5a19> has joined #yocto13:00
qschulzfbre: the partition might be mounted already?13:01
fbreyes, it is13:01
fbreit's my lowest layer in the overlayfs13:02
*** rfuentess <rfuentess!~rfuentess@2a01:598:b028:f364:8db6:b968:2b79:5a19> has quit IRC (Ping timeout: 252 seconds)13:02
fbreProbably I have put the .wic.gz file to flash first, then reboot and call bmaptool from the initramfs (before the root filesystem is mounted so to speak)13:03
fbre*have to put13:03
*** yates <yates!> has joined #yocto13:07
*** Belsirk is now known as rfuentess13:07
yatesis there a way to get one of the yocto manuals, e.g., the sdk-manual, as a pdf13:07
qschulzyates: I don't know if there's a download link already but if you compile the docs yourself with `make latexpdf` you should get that13:09
yatesok that's reasonable, thanks qschulz13:10
qschulzdocs are either in poky/documentation or yocto-docs git repo13:10
JosefHolzmayr[m]any idea why an esdk setup would fail like that:
rburtonbecause esdk hates you13:23
JosefHolzmayr[m]how sad.13:24
JosefHolzmayr[m]will it help if i bribe esdk with cookies and beer?13:24
jonmasonyou can mix beer and cookies13:24
jonmasonbeer needs salty/savory13:24
JosefHolzmayr[m]thats illegal in at least 42 states.13:25
jonmasonnow beer and a nice, soft pretzel13:25
JosefHolzmayr[m]but i don't want no cheese now, i want an installed esdk13:25
qschulzcheese is not for you Josef13:26
jonmasonI want cheese now13:26
qschulzor are you the one to bribe to get a working esdk?13:26
jonmasonok, we will give JosefHolzmayr[m] cheese if he gets the esdk working13:26
JosefHolzmayr[m]but anways, all i can see is a variety of setscene tasks failing with exit code 1.13:34
JosefHolzmayr[m]and no clue why.13:34
yatesi'm trying to do some analysis on do_populate_sysroot for libgcc via "bitbake -c populate_sysroot libgcc" but yocto isn't running the task because it things it's already complete. is there a way to remove state information for just this task of just this recipe so bitbake will rerun?13:35
yatesi'm hacking the run.do_populate_sysroot functions so i can see better what's happening13:37
qschulzyates: -f13:38
yatesqschulz: thanks!13:43
JosefHolzmayr[m]hum. standard sdk installs, and as it also brings runqemu it might even be good enough for my use case. but something no worky again
JosefHolzmayr[m](and yes, i sourced the environment. otherwise it wouldn't be on the path, obviously)13:51
*** rcw <rcw!~rcwoolley@> has joined #yocto13:51
smurrayJosefHolzmayr[m]: I think this makes you the eSDK maintainer, have at it13:56
JosefHolzmayr[m]right now i'm substantially more confused than even usual for me.13:59
*** sakoman <sakoman!> has joined #yocto14:01
smurrayJosefHolzmayr[m]: not a lot of people use eSDK, and it's lightly maintained, so I was joking that you're the maintainer now since you're using it14:02
smurrayJosefHolzmayr[m]: fray may be the person with some ideas, he poked at it a bit recently14:02
JosefHolzmayr[m]smurray: ah okay. thats what you meant.14:03
*** Guest22 <Guest22!~Guest22@> has joined #yocto14:20
*** Guest22 <Guest22!~Guest22@> has quit IRC (Client Quit)14:21
*** mtudan <mtudan!~mtudan@> has joined #yocto14:22
mcfriskis anyone aware of an NXP/Freescale kernel tree where 5.4.y stable updates would be merged already? I see but not sure of the support status on imx814:22
mcfriskotavio: ^14:23
*** mtudan <mtudan!~mtudan@> has quit IRC (Client Quit)14:23
*** mtudan <mtudan!~mtudan@> has joined #yocto14:25
*** mtudan <mtudan!~mtudan@> has quit IRC (Client Quit)14:28
*** mtudan <mtudan!~mtudan@> has joined #yocto14:29
*** mtudan <mtudan!~mtudan@> has quit IRC (Client Quit)14:29
*** mtudan <mtudan!~mtudan@> has joined #yocto14:29
qschulz seems to be the last 5.414:30
qschulzthough since they are actively working on 5.10 AFAICT, I would say there might not be any future update of this branch?14:31
mcfriskqschulz: yes, that's the crappy, buggy version that we use. Not good. Need a newer 5.4.y to fix lots of crashes in non-SoC parts of the kernel14:31
smurraymcfrisk: linux-fslc in dunfell branch of meta-freescale is on 5.4.119...14:33
smurraymcfrisk: I think Andrey probably moved onto the 5.10 kernels instead, might be worth asking him14:34
mcfriskwhat was the fslc relationship to meta-imx?14:34
smurraymeta-imx is NXP's own thing AFAIK, no community contributions14:35
smurraybut that's probably a question for otavio as I'm likely missing some nuances14:35
qschulzyes that's my understanding too14:35
mcfrisk has merged v5.4.14514:36
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto14:36
smurraymcfrisk: probably worth just trying pointing at it.  if it seems good, you could try submitting the uprev to meta-freescale for dunfell14:37
mcfrisksadly I need to work with intermediate $VENDORS and push them to right direction.14:38
fbremeta-freescale branch e42aa48f5274b335a560e3193abb86e25f52e25c works for i.mx814:40
fbre(latest hardknott)14:41
fbregit clone --branch hardknott git://
fbrecd meta-freescale14:42
fbregit checkout e42aa48f5274b335a560e3193abb86e25f52e25c14:43
smurraysure, even dunfell works for i.MX8, the specific ask was for a kernel closer to upstream 5.4.y14:48    says     LINUX_VERSION = "5.4.129"  from KBRANCH = "5.4-2.3.x-imx"14:50
fbreworks even with RT patch14:52
smurraysure, and upstream is at .147, I assume mcfrisk meant he wanted something closer to that14:54
fbrenot with RT patch, and RT patch is good for i.mx814:55
Ad0I get from curl on an ssl site I know works well in my regular browser "curl failed to verify the legitimacy of the server and therefore could not ... "14:55
smurrayfbre: mcfrisk said nothing about the RT patch, if it works for you, great14:55
rburtonAd0: is ca-certificates installed14:57
Ad0I installed the root certificate14:59
*** jd40 <jd40!> has joined #yocto15:02
Ad0I run update-ca-certificates but it does not show up in /etc/ssl/certs/ca-certificates.crt15:03
Ad0it successfully creates a link in /etc/ssl/certs tho15:03
jd40Hey folks, I was working on some recipes and was wondering something.15:04
jd40if I have a DEPENDS="recipe" that recipe has a PV and PR, is there a good way to retrieve those in the current recipe?15:04
rburtonnot really15:05
jd40I was afraid of that, well thanks anyway15:05
kergothHmm, does Yocto maintain info about what CVEs were fixed by a recipe upgrade? The patches get dropped, so the CVE: metadata isn't there any longer, is there a database for that, or not covered anywhere?15:06
*** ThomasD13 <ThomasD13!> has quit IRC (Ping timeout: 252 seconds)15:06
rburtonyou can infer it from the cve database15:06
rburtonwe tend to go and get that fixed if its incomplete15:06
qschulzjd40: if you explain what you are trying to achieve maybe we can guide you through a proper solution?15:07
kergothrburton: which one, nvd?15:09
*** eduardas <eduardas!~eduardas@> has quit IRC (Quit: Konversation terminated!)15:10
jd40I'm working on our update package that can be used to update deployed systems, basically it's a archive of several build artifacts15:11
*** tre <tre!> has quit IRC (Remote host closed the connection)15:13
*** vd <vd!> has joined #yocto15:13
qschulzjd40: you can deploy a file from each recipe that is providing their version and make the recipe building the archive read those files, you need to not forget to add the proper dependency on the deploy task for that archive recipe otherwise you might have races15:13
*** jd40 <jd40!> has quit IRC (Quit: Client closed)15:14
*** jd60 <jd60!> has joined #yocto15:14
*** jd60 is now known as jd4015:15
jd40qschulz that might indeed be a good solution, I'll see if I can make that work, thank you.15:17
Ad0qschulz, rehash: warning: skipping duplicate certificate in gd-class2-root.pem15:18
Ad0it's already there ...15:18
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)15:21
fbrehmm grmpf.... calling bmaptool from my initramfs leads to this error:15:30
fbre  File "/usr/lib/python3.8/", line 675, in __getitem__15:30
fbre    raise KeyError(key) from None15:30
fbreKeyError: 'PATH'15:30
fbreAny idea what I can do?15:30
RPfbre: set the PATH environment variable in the call site?15:34
fbreThe .sh script sets PATH a few lines before15:34
fbrebefore the call of bmaptool15:35
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Quit: Konversation terminated!)15:37
kergothfbre: forget to export it?15:38
Ad0rburton, it was the server cert that was misconfigured15:40
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto15:41
otaviomcfrisk: 5.4 is being updated but what you need?15:47
otaviomcfrisk: we have it on dunfell for example15:47
fbrekergoth, yeah good hint. Adding "export" helps15:49
mcfriskotavio: I'd need an 'NXP' blessed tree with 5.4 LTS merges which can be used on imx8 by vendors. I'd point them to it instead of giving me v5.4.70 with a lot of known bugs like fuse crashes15:51
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)15:51
*** fbre <fbre!~fbre@> has quit IRC (Quit: Client closed)15:57
*** rfuentess <rfuentess!~rfuentess@2a01:598:88b1:1122:8db6:b968:2b79:5a19> has quit IRC (Remote host closed the connection)16:00
frayInternally our guys are working off master of tcf-agent because it fixes issues like walking arm thumb code and better supporting clang 12.  Should I put together a tcf-agent update or master?  (There hasn't been a new "release", and the current tcf agent is based on 1.7.0 tag.16:05
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)16:05
moto-timofray: seems like a good idea16:09
frayok.. so I'm not stupid.. (My problem is I have no way to test it, but like I said, another team is 100% using the latest code.  So I know it 'works for them'.  I just hate keeping patches internal.)16:10
*** florian <florian!> has quit IRC (Quit: Ex-Chat)16:13
*** jd40 <jd40!> has left #yocto16:14
*** fitzsim <fitzsim!> has joined #yocto16:18
*** zpfvo <zpfvo!~fvo@> has quit IRC (Remote host closed the connection)16:23
*** rcw <rcw!~rcwoolley@> has quit IRC (Quit: Leaving)16:28
*** gsalazar <gsalazar!~gsalazar@> has quit IRC (Ping timeout: 268 seconds)16:32
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto16:40
*** rcw <rcw!~rcwoolley@> has joined #yocto17:00
*** otavio <otavio!> has quit IRC (Remote host closed the connection)17:17
moto-timofray: especially since the 1.7 branch hasn’t seen any attention since 2018. It would be nice if upstream would do a new “release”17:18
*** otavio <otavio!> has joined #yocto17:28
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto17:38
*** prabhakarlad <prabhakarlad!> has joined #yocto17:45
fraymoto-timo sent.. I feel a bit dirty with the commit message though, as I really don't know more about it to better comment on the change.. :(17:51
frayI just know the reason _I_ was paying attention to it17:51
*** florian <florian!~florian@> has joined #yocto17:54
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)17:57
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto18:03
*** frieder <frieder!> has quit IRC (Quit: Leaving)18:20
*** florian <florian!~florian@> has quit IRC (Ping timeout: 252 seconds)18:29
JosefHolzmayr[m]fray: hello my last straw... any idea how i could nail down this?
frayI had that happen before when things were either missing from the sstate-cache or files were getting corrupted..18:39
fray(the faled exit code 1 thing)18:39
frayif you can figure out what that is (I'm guessing lack of the state-cache file).. then we can traceback why..18:39
yannda bit off-topic: anyone investigated the idea of using bitbake to build a downstream distro of debian/fedora/whatever ?  The idea would be to have a "magic layer" providing upstream deb/rpm with mostly do_fetch and do_package_write_{deb,rpm}, and the necessary bits to make them usable in sysroots18:46
yanndthat would not really help to modify packages, only to add custom distro-specific packages - modified packages would have to be translated to bb's, so yes that's not perfect18:48
yanndthe upside would be the ability to customize vitrually any distro18:49
sgwHi Guys, I should probably know this, but will consult this oracle, is there a set of tests for the SDK? I know that eSDK has a couple of test cases in the oe-selftest. Thx18:52
JosefHolzmayr[m]yannd: look at what the isar guys or elbe are doing - its basically what you described, for debian.18:57
moto-timoyannd: for Debian that is what isar does
JosefHolzmayr[m]fray: was distracted, sorry. hm. sadly this happens on the "official" esdks, and on something that i created. i suspect something wrong in the target container to run it, but i have no clue on how to approach it.18:59
JosefHolzmayr[m]moto-timo: english speaking people say: "great minds think alike". german speaking people say: "two idiots, one idea"19:00
moto-timoyannd: in theory if you could get fedbootstrap integrated you could do similar for Fedora.19:00
yanndnice, thx!19:00
frayI've only seen it when a disk is broken (corrupting files) or hashes are changing during extraction..19:01
fraybut if you can dig into the eSDK logs you should be able to find the error triggering the exit 1..19:01
frayI'm guessing [without anything further] that the setscene file is not there, so 'file not found'19:01
JosefHolzmayr[m]moto-timo: hi519:03
fraythe only time I saw that behavior is when the eSDK config and the actual config were out of sync [or things ran in the wrong order]..19:05
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Remote host closed the connection)19:10
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto19:10
moto-timosgw: do you mean beyond
*** mtudan <mtudan!~mtudan@> has quit IRC (Ping timeout: 256 seconds)19:15
moto-timoyannd: there also an effort a while back to use Fedora and other distro sources/patches
*** florian <florian!> has joined #yocto19:24
jonmasonRP: I think I have virtio graphics working.  Just trying to do a little more testing before I send out the patch19:31
jonmasonThat comment in the bugzilla was 1/2 correct.  It's not listed there, but there is a new way of doing it19:31
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 268 seconds)19:35
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)19:38
RPjonmason: ah, cool!19:55
yatesfind . -print0 | cpio --null -pdlu $dest20:02
yatesthis line ^^^^^ is in an oe .bbclass.20:03
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)20:03
yateswhat does -pdlfu signfy?20:03
yanndmoto-timo: nice too, thx :)20:06
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto20:06
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto20:08
RPyates: "man cpio" ;-)20:11
*** florian <florian!> has quit IRC (Ping timeout: 260 seconds)20:19
*** yannd <yannd!~yann@> has quit IRC (Ping timeout: 265 seconds)20:31
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 268 seconds)20:36
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: Textual IRC Client:
vdDo you need to use := with ${THISDIR}?20:44
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)20:48
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto20:52
vdfrom a recipe_%.bbappend file, ${PV} is literally '%'. What should I do to get the proper package version?21:03
*** Vonter_ <Vonter_!~Vonter@user/vonter> has joined #yocto21:03
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)21:04
manuelwtf I added ptest to my DISTRO_FEATURES and now it's rebuilding more or less everything. Altough I didn't put ptest-pkgs in the IMAGE_FEATURES. Why is that?21:06
manuelI'm including only one -ptest package so I'd have expected to see that one getting rebuilt only.21:07
RPmanuel: ptests often have a lot more dependencies and it has to build them for everything even if you don't add them all to an image21:10
*** amitk_ <amitk_!~amit@> has joined #yocto21:21
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 268 seconds)21:24
*** xmn <xmn!> has joined #yocto21:32
*** amitk_ <amitk_!~amit@> has quit IRC (Ping timeout: 268 seconds)21:43
*** markus5h[m] is now known as mahu[m]22:02
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)22:05
*** jwillikers <jwillikers!> has joined #yocto22:16
*** yates <yates!> has quit IRC (Quit: rcirc on GNU Emacs 25.2.2)22:16
*** florian <florian!> has joined #yocto22:22
*** rcw <rcw!~rcwoolley@> has quit IRC (Quit: Leaving)22:51
RPjonmason: thanks, I put the patches on the AB for testing (along with another slighly risky patch of mine)23:04
*** bluelightning <bluelightning!~paul@2406:e003:1528:db01:14e8:4ee3:ae7c:4984> has joined #yocto23:05
jonmasonGood.  I made sure it worked locally but didn't run testimage23:06
*** florian <florian!> has quit IRC (Ping timeout: 268 seconds)23:12
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)23:19
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)23:33
*** dev1990 <dev1990!~dev@> has quit IRC (Quit: Konversation terminated!)23:40

Generated by 2.17.2 by Marius Gedminas - find it at!