Tuesday, 2022-03-08

*** florian_kc <florian_kc!~florian@dynamic-093-133-013-068.93.133.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)00:23
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)01:53
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)02:19
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto03:04
*** Thorn_ <Thorn_!~Thorn@user/thorn> has quit IRC (Ping timeout: 272 seconds)03:33
*** amitk <amitk!~amit@103.208.71.36> has joined #yocto03:33
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto03:35
*** jclsn71 <jclsn71!~jclsn@149.224.231.155.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto03:40
*** jclsn7 <jclsn7!~jclsn@149.233.138.126.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 256 seconds)03:42
*** jclsn71 is now known as jclsn703:42
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)05:05
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto05:06
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 256 seconds)05:08
*** camus1 is now known as camus05:08
*** davidinux <davidinux!~davidinux@net-188-153-130-222.cust.vodafonedsl.it> has quit IRC (Ping timeout: 240 seconds)05:25
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto05:29
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto05:50
*** aclaws <aclaws!~dave@node-1w7jr9ppfiid0mfwihixdoerh.ipv6.telus.net> has quit IRC (Quit: aclaws)06:03
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto06:03
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)06:05
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 240 seconds)06:13
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)06:25
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto06:26
*** Etheryon <Etheryon!~textual@79.113.77.204> has joined #yocto06:39
*** cb5r <cb5r!~cb5r@user/cb5r> has joined #yocto07:05
*** cb5r_ <cb5r_!~cb5r@user/cb5r> has joined #yocto07:05
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto07:07
*** cb5r <cb5r!~cb5r@user/cb5r> has quit IRC (Ping timeout: 256 seconds)07:10
*** cb5r_ is now known as cb5r07:10
jclsn[m]Is there a way to run menuconfig on defconfigs that are inside the layer?07:18
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto07:19
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:21
Etheryoncan anyone point me to a guide on how to configure grub in yocto? Or an example?07:27
*** frieder <frieder!~frieder@i59F72BBB.versanet.de> has joined #yocto07:32
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:33
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has joined #yocto07:34
EtheryonI've ran out of google pages :D07:37
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto07:38
*** NurettinTopalak <NurettinTopalak!~NurettinT@46.221.0.162> has joined #yocto07:46
NurettinTopalakDo you have any suggestions for writing yocto image to more than 50 devices? Is there something like automatic image write tool available or how can i do it?07:49
NurettinTopalakI write to each device one by one with the bmaptool command. I want to automate this.07:49
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto07:53
*** dgriego_ <dgriego_!~dgriego@user/dgriego> has quit IRC (Ping timeout: 240 seconds)07:53
EtheryonI've been thinking about that as well, maybe boot over network? I haven't looked too much into that yet07:54
Etheryonand create an image that auto-installs (kinda like a live cd?)07:55
NurettinTopalakGoogle dev board's image writing technique is good  but i am using cm4, SD card is embedded.07:56
*** jpnurmi <jpnurmi!jpnurmi@user/jpnurmi> has joined #yocto07:58
*** sergioprado <sergioprado!~sergiopra@201.56.173.82> has joined #yocto08:01
*** sergioprado <sergioprado!~sergiopra@201.56.173.82> has quit IRC (Client Quit)08:02
NurettinTopalakWriting Mendel to the SD card. Insert the SD card into the Google-Dev-Board, then you set the boot settings from the pins on the device then write the image to eMMC. After that, undo the setting you made on the board.08:04
NurettinTopalakhttps://coral.ai/docs/dev-board/get-started/#flash-the-board08:05
*** mckoan|away is now known as mckoan08:05
mckoangood morning08:05
NurettinTopalakmorning08:06
NurettinTopalakto write an image to cm4,  need to plug it into RPI-CM4-IOBOARD08:06
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto08:12
*** Guest22 <Guest22!~Guest22@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has joined #yocto08:12
Guest22hello08:12
NurettinTopalakhi08:14
Guest22updated the recipe in our own meta-project to fetch a newer kernel, it's all working and the kernel is compiling : Kernel: arch/arm/boot/Image is ready08:15
Guest22|   Kernel: arch/arm/boot/zImage is ready08:15
Guest22|   Kernel: arch/arm/boot/uImage is ready08:15
Guest22However it seems, as opposed to our previous kernel version, the device tree is not created:  make[1]: *** No rule to make target 'arch/arm/boot/dts/rzn1d400-db.dtb'.  Stop.08:15
Guest22I must have missed something, could use a pointer ... (no pun intended)08:16
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:16
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)08:25
*** mrybczyn <mrybczyn!~mrybczyn@80.215.234.43> has joined #yocto08:26
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:26
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)08:29
*** Guest22 <Guest22!~Guest22@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has quit IRC (Ping timeout: 256 seconds)08:33
LetoThe2ndyo dudX08:33
shoraganrburton, you said yesterday to Emantor that the kernel debugging symbols would be in the -dbg package08:44
LetoThe2ndWhat might be a good strategy for a package that comes on a dunfell branch, but is deprecated? Keep the initial version recipe around forever as PREFERRED_VERSION, albeit the really preferred version is newer?08:44
shoragani don't see anything that linux-yocto would do differently. i don't get any kernel-dbg package, though :)08:45
shoraganthere's kernel-vmlinux, which contains the unstripped vmlinux, so that's fine. but i'm still looking for the debug symbols of the kernel modules08:49
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:00
*** NurettinTopalak <NurettinTopalak!~NurettinT@46.221.0.162> has quit IRC (Quit: Client closed)09:01
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c2a0:8640:7a3:73e3:df4:afe1> has joined #yocto09:05
*** tgamblin_ <tgamblin_!~tgamblin@2607:fea8:c2a0:8640:7a3:73e3:df4:afe1> has quit IRC (Ping timeout: 240 seconds)09:05
*** Guest22 <Guest22!~Guest22@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has joined #yocto09:12
shoragani tried with MACHINE=qemuarm on honister, with enabled features/debug/debug-kernel.scc, and i don't have a -dbg either. what am i missing?09:15
RPshoragan: you need master for this09:23
RPshoragan: it was a recent change09:24
shoraganah!09:24
shoraganRP, https://git.yoctoproject.org/poky/commit?id=d756b346f248df47b0540644adb1d0f17bcc4b6e + some related commits?09:29
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:33
RPshoragan: yes, that looks right09:41
RPshoragan: it wasn't entirely straight forward09:42
shoraganyes, looks like it. another reason to move to master :)09:43
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 256 seconds)09:45
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto09:45
*** mihai <mihai!~mihai@user/mihai> has joined #yocto09:47
*** sstiller <sstiller!~sstiller@p200300f07f1636000450e69370442a0c.dip0.t-ipconnect.de> has joined #yocto10:01
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 240 seconds)10:20
*** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has quit IRC (Ping timeout: 256 seconds)10:39
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto10:41
Saur[m]RP: I have sent the updated patches to the list now. The second patch is reworked so there should be no differences in the output except for the fixed progress bar. The patch adding a progress bar for the setscene tasks is dropped. I've also added a patch that adds the number of running tasks to the silent mode,  and removes the word "currently" from the normal mode,  thus unifying the outputs between the modes. I think it improves the output, but11:09
Saur[m]since we seem to have very different opinions when it comes to the UI, I'll leave it to you to decide whether you want it or not.11:09
*** Lihis <Lihis!~Lihis@2001:41d0:e:f34::1> has quit IRC (Quit: Quitting)11:12
*** Lihis <Lihis!~Lihis@2001:41d0:e:f34::1> has joined #yocto11:13
*** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has joined #yocto11:18
Wouter0100Hello! I'm having issues with a USB 2.0 to 8 x RS-232 serial adapter. On raspbian it works like a charm, but on a custom build OS based on Poky - it slows down all our RPi's to a crawl. After I've plugged in the adapter, I'm nearly unable to login through SSH, and if I'm already logged in through SSH and I plug in the adapter - it starts to respond11:20
Wouter0100very very slowly to commands to a point that it is nearly unresponsive. If U unplug the adapter, it starts to properly respond again. Is this a known issue or any suggestions where to look for a potential fix?11:20
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 252 seconds)11:24
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto11:25
qschulzWouter0100: Distros are known to carry a set of patches on top of packages and kernels. It is likely they have something fixing some issues in the kernel that they haven't upstreamed or the kernel version you build in Yocto is too old11:26
qschulzsimilar things could happen to one of your userspace packages too11:26
qschulzI don't know11:26
Guest22hello;-)11:26
*** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has quit IRC (Ping timeout: 272 seconds)11:27
Guest22I have recently changed to dunfell from rocko, how do I determine the version of yocto/dunfell I have?11:27
*** mckoan <mckoan!~marco@host-79-3-92-72.business.telecomitalia.it> has joined #yocto11:28
rburtonhow did you change?11:28
Wouter0100qschulz: Yeah, we also have an userspace package which is showing performance issues. This is not really an issue, but the adapter issue is. I'll have a look which kernel version we're building into Yocto.11:28
*** sgw <sgw!~swold_loc@user/sgw> has quit IRC (Ping timeout: 240 seconds)11:31
Guest22rburton:git checkout dunfell11:33
Guest22simple11:33
Guest22lol11:33
rburton$ git describe  origin/dunfell11:34
rburtonyocto-3.1.14-102-g9426c3c83d11:34
rburtonassuming you have the same commit, 3.1.14 + 102 commits11:34
Guest22yocto-3.1.14-52-gc8987e7bca11:37
Guest22brilliant thanks11:37
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds)11:38
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto11:47
barathhi all. is there a way to specify which version of gcc yocto should use for native recipes? googling turned up BUILD_CC, but that doesnt seem to do that and I cant find documentation for it12:06
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)12:06
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has joined #yocto12:07
rburtonbarath: for native we use the host compiler12:08
rburtonif 'gcc' isn't right, set BUILD_CC and friends12:08
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Ping timeout: 272 seconds)12:18
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto12:23
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 256 seconds)12:25
*** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:4173:8849:3059:8bf5> has joined #yocto12:28
RPSaur[m]: your patch is a nightmare to review since it is still doing things like "self.quiet == 0" -> "not self.quiet" which has no functional change but makes me wonder what else is just being changed for cosmetic reasons :(12:40
RPSaur[m]: to be honest I'd prefer a simpler patch than that, rather than rewriting so much12:40
rburtonafter branch we should run bitbake through black and reformat/stylize it :)12:42
JaMa4 spaces for the win12:45
* JaMa hides12:45
*** Guest22 <Guest22!~Guest22@cpc142184-mcam2-2-0-cust140.18-3.cable.virginm.net> has quit IRC (Quit: Client closed)12:49
kroonsomeone should rewrite bitbake in C13:01
kroonor, i can go sofar as rust13:02
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Ping timeout: 256 seconds)13:16
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto13:37
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 260 seconds)13:37
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 256 seconds)13:38
*** camus1 is now known as camus13:38
RPkroon: I once intended to do that (C). It doesn't actually make sense when you get into the details13:40
kroonRP, I believe you. But I wish I knew more about optimizing python code.13:44
RPkroon: There is a profile option to bitbake which generates reports which tell you where it spends all the time13:45
JaMachromium.do_compile for me :)13:45
kroonRP, i did have a look at that at one point in time, but I got lost :-/13:46
* RP wishes he could spend more time on optimisation13:46
RPbasically it comes down to spotting things which can be made more efficient or not done at all (see the recent files removal from the sysroot)13:47
kroonRP, running anonymoys python code is a big bottleneck when parsing ?13:47
RPkroon: yes, it is one of the big time sinks13:48
kroonRP, yes, those file removals are nice13:48
RPkroon: the variable dependency code is another pain point but I'm not sure what we can do about that13:48
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:51
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto14:05
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has joined #yocto14:18
*** lpapp <lpapp!~lpapp@ec2-35-158-255-21.eu-central-1.compute.amazonaws.com> has joined #yocto14:32
*** lpapp <lpapp!~lpapp@ec2-35-158-255-21.eu-central-1.compute.amazonaws.com> has left #yocto14:32
Saur[m]RP: Ok, I've extracted the two minor code clean ups to a separate patch now.14:34
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Quit: Leaving)14:40
JPEWJPEW14:44
JPEWpaulg: IIRC the load average does include tasks waiting on Disk I/O14:45
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)14:58
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto14:59
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)15:04
rburtonRP: qemu cpe's updated so they'll be gone next report15:05
RPrburton: awesome, thanks15:05
RPrburton: vim upgraded too15:05
rburtonyeah just need to get a seatd upgrade out really15:05
RPpaulg: you were offline when I replied yesterday but the scheduler in bitbake in plugable and making it pause new tasks starting shouldn't be hard15:06
RPpaulg: vmeson had some interesting ideas about using some of the new load indications from recent kernels which did sound promising15:06
rburtonRP: and libsolv CPEs updated too15:12
RPrburton: great, that should handle the tidal wave of this week's issues!15:13
*** cb5r <cb5r!~cb5r@user/cb5r> has quit IRC (Quit: cb5r)15:19
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto15:31
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has joined #yocto15:39
moto-timoLife is good when you get a second set of eyes on your code.15:42
moto-timoThank you rburton15:42
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 252 seconds)15:42
rburtonmoto-timo: <cough> about to send another series15:42
rburtonand there's another bundle after that about to get the final build test15:42
rburton(which involves a world build and then diffoscope of the rpms)15:43
RPrburton: another series? :)15:47
moto-timoLol15:47
RPmoto-timo: autobuilder can't keep up!15:50
* moto-timo clones the AB cluster15:51
*** vvn <vvn!~vivien@bras-base-mtrlpq2848w-grc-41-70-53-240-211.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.4)15:55
*** vvn <vvn!~vivien@bras-base-mtrlpq2848w-grc-41-70-53-240-211.dsl.bell.ca> has joined #yocto15:58
paulgRP, maybe I'll go look at it and see how scary it is.  Like I said yesterday, I need to retire to have more "chase a squirrel" time.15:58
paulgJPEW, yea I guess if the disk is busy with trying to swap, then that will be implicitly reflected in tasks in D blocked on i/o16:00
RPpaulg: https://git.yoctoproject.org/poky/tree/bitbake/lib/bb/runqueue.py#n13516:02
paulgI'm not sure if a task shows load if it is waiting on a page fault to be filled that is waiting on swap though.16:02
RPpaulg: it is a lovely looking rabbit hole :)16:02
paulge.g.  no i/o pending - just 5 tasks blocked on malloc() waiting for a page...16:03
paulg(no task generated i/o pending that is, via read() write() or similar...)16:03
rburtonRP: neither can my machine, it's build numpy about 20 times today16:04
JPEWpaulg: Not sure. If the page fault make the task go into uninterruptable sleep, then yes. Can't find the answer to that, but maybe yes since other disk I/O is uninterruptable?16:06
JPEWMaybe someone with more kernel knowledge knows16:06
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 272 seconds)16:10
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto16:10
paulgeither way, since we have access to /proc/swaps - we don't really need to try and "guess" if we have dipped into the swap pool.16:10
JPEWpaulg: Sure.... I'd be a little concerned about trusting that since things can get put there and never pulled out even when the load goes back down16:12
JPEWWell, not never, but on demand, and if there is no demand....16:12
* paulg takes note of the file/function RP has pointed at and tries to not get sucked into the rabbit hole today.16:12
paulgJPEW, yea - you wouldn't look for it to go back to zero - since unused getty and cups and other cobweb infested cruft goes out there to rot until the next reboot.16:13
RPpaulg: there are some subclasses below that too FWIW16:14
paulgyou'd want to watch for increases, and jitter on the used number as a simple 1st pass metric.16:14
paulgI think for now I'd be more apt to implement the COMPILE_EXCLUSIVE=1 and set that for some small subset of uber-massive turds.16:14
paulganything that tries to have an AI aspect to it just turns out to be annoying and wrong all the time.16:15
paulgTake the hateful OOM killer as a prime example.16:15
JPEWpaulg: in our devices, we always make our UI app the most preferred thing for the OOM to kill; it's annoying16:20
paulgI was talking this over with our local version of halstead here - what size of swap to configure -  I tend to just add a small amount of swap (1G) so unused crap can be evicted, but with no intention for it to be in active use during a build - and we were wondering if this creates a pathologically bad case that is worse than having no swap at all once you are at 90% mem usage...16:20
paulgKind of like having the Autobahn populated with 100m of gravel washboard every kilometre...16:21
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)16:25
rfs613paulg: I guess it is just certain packages causing problems? I don't have any issues with needing swap in my builds... 16 jobs running, 32G of RAM total, rarely see more than a few GBs in use during build.16:26
paulgrfs613, it depends if your build uses libsrvg - which in turn triggers rust and cargo native ; which largely stall a 16G machine and guaranteed OOM an 8G machine.16:29
paulgthe theory is that *if* you don't try and build anything else while building rust, cargo .... then these "low ram" machines might be able to be used for another couple years by Joe Average out there.16:30
rfs613"Librsvg aims to be a low-footprint library [...]" -- so I guess they have a different definition of low footprint... or maybe they ignore the build aspect, and just mean runtime.16:32
paulgyea - for sure build vs. runtime. As an old fart who has been using linux since the early 1990s, I find the RSS number of rust while watching a build just mind boggling.16:33
paulgpretty sure it must be trying to compute the number of stars in the universe or something as part of the optimizer....16:34
rfs613so, after they finish rewriting everything in Rust, they only problem will be there's not enough ram or CPU in the planet to build it ;P16:34
paulgpretty much.16:35
paulghopefully if the thing ever gets traction then some attention will turn from making it work to making it suck less.16:35
*** spyre <spyre!~spyre@2804:14d:baa3:456f:e9b1:9790:3bff:2345> has joined #yocto16:35
spyreHi cool people. Long shot but, anybody has any information on using u-boot on the phycore-am335x?16:37
rfs613spyre: don't have one myself, but looking at u-boot source, there seems to be a .dtsi file for it, and also MAINTAINERS has entry16:41
rfs613seems it is a SOM and it's used on some carriers, "regor" and "wega", which look like they are supported.16:42
spyreOh okay, I see it! I think I can work with that (I use a different carrier atm). I'll probably have to write a recipe for it, right?16:43
rfs613spyre: well there are already plenty of recipes for u-boot, including in poky and in meta-ti. So probably only need to tweak it.16:45
*** Etheryon <Etheryon!~textual@79.113.77.204> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)16:46
rfs613spyre: but you should probably first tryi building u-boot and getting it working, manually (outside of yocto). Find out if you need to modify u-boot sources, etc. Once you have that, integrating it into yocto build is a separate step.16:46
spyrerfs613: oh okay, I see it. I think the dots connected in my head now :)  I'll see if I can get this to work (and try to upstream it as well, if it does). Thanks a lot for the pointers.16:48
*** spyre <spyre!~spyre@2804:14d:baa3:456f:e9b1:9790:3bff:2345> has quit IRC (Ping timeout: 256 seconds)16:53
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto16:58
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto17:02
kevinrowlandHello folks. Curious about this bit from the mega manual regarding `IMAGE_FSTYPES`: "Due to the way the OpenEmbedded build system processes this variable, you cannot update its contents by using _append or _prepend. You must use the += operator to add one or more options to the IMAGE_FSTYPES variable." I've got a vendor layer that uses `?=` to17:08
kevinrowlandassign to `IMAGE_FSTYPES`, so when I use `+=` in my `local.conf` the vendor changes aren't applied on top of my `local.conf` changes. I _can_ use `+=` in my own machine conf and that works fine because it's applied after the vendor layer.  Can someone enlighten me as to why we can't use _append though? Is it because the  `IMAGECLASSES`17:08
kevinrowlanddefinitions at the top of `image.bbclass` use `bb.utils.contains(IMAGE_FSTYPES, ...)` and so the `IMAGE_FSTYPES` variable can't use late-binding / late-expansion?17:08
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)17:15
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed)17:30
vmesonpaulg: : we do have support for make -l  and use it in the YP Autobuilder (  https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=5c5fc7bc )  but I haven't looked at  the load for Rust/cargo but it seems like -l should work:17:30
vmeson   https://github.com/meta-rust/meta-rust/commit/647b976da2a9161ceb01ad477216480fc1c88af817:30
paulgI'll have a look after this meeting17:31
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto17:32
*** nateglims <nateglims!~nateglims@72-21-196-67.amazon.com> has joined #yocto17:33
vmesonpaulg: thanks. As RP mentioned, the problem with loadavg limiting is that it's not updated quickly. We plan to use /prod/pressure info when it's there in newer kernels.17:33
*** sstiller <sstiller!~sstiller@p200300f07f1636000450e69370442a0c.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)17:33
*** mrybczyn <mrybczyn!~mrybczyn@80.215.234.43> has quit IRC (Quit: Client closed)17:36
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto17:37
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 256 seconds)17:39
*** camus1 is now known as camus17:39
*** nateglims <nateglims!~nateglims@72-21-196-67.amazon.com> has quit IRC (Quit: Client closed)17:41
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:42
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)17:43
kevinrowlandMy IRC client disconnected me.. did anyone respond to my question about `IMAGE_FSTYPES` above? :)17:43
*** nateglims <nateglims!~nateglims@72-21-196-67.amazon.com> has joined #yocto17:43
paulgkevinrowland, https://www.yoctoproject.org/irc/17:46
*** frieder <frieder!~frieder@i59F72BBB.versanet.de> has quit IRC (Remote host closed the connection)17:46
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds)17:47
*** mckoan is now known as mckoan|away18:00
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 240 seconds)18:01
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed)18:06
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has joined #yocto18:15
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto18:24
kevinrowlandpaulg: tyvm18:24
*** nateglims <nateglims!~nateglims@72-21-196-67.amazon.com> has quit IRC (Quit: Client closed)18:36
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto18:56
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has quit IRC (Read error: Connection reset by peer)18:56
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has joined #yocto18:56
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)19:01
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)19:10
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has joined #yocto19:14
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 240 seconds)19:37
*** Piraty <Piraty!~irc@user/piraty> has quit IRC (Quit: -)19:38
*** Piraty <Piraty!~irc@user/piraty> has joined #yocto19:40
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto19:42
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto19:54
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)20:04
*** yannd <yannd!~yann@88.120.44.86> has joined #yocto20:07
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)20:12
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto20:14
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has joined #yocto20:32
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)20:37
*** marc2 <marc2!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has quit IRC (Ping timeout: 256 seconds)20:55
*** marc2 <marc2!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has joined #yocto20:58
*** amitk <amitk!~amit@103.208.71.36> has quit IRC (Ping timeout: 256 seconds)21:15
*** pasherring <pasherring!~pasherrin@2001:8a0:ec55:b200:4173:8849:3059:8bf5> has quit IRC (Quit: Leaving)21:16
*** bluelightning <bluelightning!~paul@2406:e003:151f:d701:f456:94f8:278e:c695> has joined #yocto21:16
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has joined #yocto21:20
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)21:33
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto21:35
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has joined #yocto21:40
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto21:43
*** GillesM <GillesM!~gilles@228.100.5.84.rev.sfr.net> has joined #yocto21:56
*** GillesM <GillesM!~gilles@228.100.5.84.rev.sfr.net> has quit IRC (Client Quit)21:57
*** lucaceresoli_ <lucaceresoli_!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 252 seconds)22:30
*** u1106 <u1106!~quassel@ec2-18-193-68-189.eu-central-1.compute.amazonaws.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)22:39
*** Etheryon <Etheryon!~textual@79.113.77.204> has joined #yocto22:40
*** u1106 <u1106!~quassel@ec2-18-193-68-189.eu-central-1.compute.amazonaws.com> has joined #yocto22:42
*** Etheryon <Etheryon!~textual@79.113.77.204> has quit IRC (Ping timeout: 256 seconds)22:48
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)23:30
*** florian_kc <florian_kc!~florian@dynamic-093-132-030-127.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)23:39
*** MrFrank <MrFrank!~MrFrank@mx1.fracta.dev> has quit IRC (Read error: Connection reset by peer)23:41
*** MrFrank <MrFrank!~MrFrank@mx1.fracta.dev> has joined #yocto23:41
*** darknighte <darknighte!sid214177@user/darknighte> has quit IRC (Read error: Connection reset by peer)23:41
*** ernstp <ernstp!sid168075@id-168075.hampstead.irccloud.com> has quit IRC (Read error: Connection reset by peer)23:41
*** dl9pf <dl9pf!sid395223@id-395223.helmsley.irccloud.com> has quit IRC (Read error: Connection reset by peer)23:41
*** darknighte <darknighte!sid214177@user/darknighte> has joined #yocto23:41
*** dkl <dkl!~dkl@prometheus.umask.eu> has quit IRC (Quit: %quit%)23:41
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Remote host closed the connection)23:41
*** dkl <dkl!~dkl@prometheus.umask.eu> has joined #yocto23:42
*** wyre <wyre!~wyre@user/wyre> has joined #yocto23:42
*** dl9pf <dl9pf!sid395223@id-395223.helmsley.irccloud.com> has joined #yocto23:42
*** ernstp <ernstp!sid168075@id-168075.hampstead.irccloud.com> has joined #yocto23:42
*** bantu <bantu!~bantu@edna.bantux.com> has quit IRC (Quit: bantu)23:43
*** lettucepunch[m] <lettucepunch[m]!~lettucepu@2001:470:69fc:105::1:c900> has quit IRC (Ping timeout: 252 seconds)23:44
*** Lcvette[m] <Lcvette[m]!~lcvettema@2001:470:69fc:105::e43> has quit IRC (Ping timeout: 252 seconds)23:44
*** bantu <bantu!~bantu@edna.bantux.com> has joined #yocto23:44
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)23:47
*** lettucepunch[m] <lettucepunch[m]!~lettucepu@2001:470:69fc:105::1:c900> has joined #yocto23:57
*** Lcvette[m] <Lcvette[m]!~lcvettema@2001:470:69fc:105::e43> has joined #yocto23:59

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!