Tuesday, 2023-05-23

*** Saur <Saur!~pkj@nebula.axis.com> has quit IRC (Read error: Connection reset by peer)00:19
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has joined #yocto00:48
*** Saur <Saur!~pkj@nebula.axis.com> has joined #yocto00:52
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)00:57
*** davidinux <davidinux!~davidinux@92.118.62.78> has quit IRC (Ping timeout: 240 seconds)01:03
*** davidinux <davidinux!~davidinux@92.118.62.81> has joined #yocto01:05
*** odra_ <odra_!~odra@177.94.130.83> has joined #yocto01:12
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has quit IRC (Read error: Connection reset by peer)01:13
*** starblue <starblue!~juergen@dslb-094-221-183-025.094.221.pools.vodafone-ip.de> has quit IRC (Ping timeout: 265 seconds)01:41
*** starblue <starblue!~juergen@dslb-094-220-108-248.094.220.pools.vodafone-ip.de> has joined #yocto01:43
khempaulg: yeah, I feel annoyed too, if it gives you any comfort, I get clang to rebuild too 🙂 which is good 1+ hrs just for toolchain, I think using locked sstate might be good idea to mature02:06
*** odra_ <odra_!~odra@177.94.130.83> has quit IRC (Quit: Leaving)02:16
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 240 seconds)02:17
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto02:39
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has joined #yocto03:19
*** odra_ <odra_!~odra@177.94.130.83> has joined #yocto03:30
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has quit IRC (Read error: Connection reset by peer)03:31
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:58
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto05:00
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)05:00
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto05:01
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 256 seconds)05:43
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto05:44
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 248 seconds)05:48
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto05:48
*** starblue <starblue!~juergen@dslb-094-220-108-248.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 240 seconds)05:53
*** starblue <starblue!~juergen@dslb-094-220-115-218.094.220.pools.vodafone-ip.de> has joined #yocto05:54
Entei[m]How do you pass flags such as isa extensions used while building rust?06:19
Entei[m]All my packages follow the flags passed to gcc, but rust using llvm, does not assume the same06:20
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto06:27
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 268 seconds)06:34
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto06:52
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 240 seconds)06:54
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto06:54
RPpaulg: that looks like target gcc. Probably as you have ptests enabled. Disabling ptests will speed things up06:54
*** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto07:02
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:02
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto07:03
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 268 seconds)07:03
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto07:04
*** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has joined #yocto07:04
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Read error: Connection reset by peer)07:05
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)07:05
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto07:06
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto07:06
*** chep` <chep`!~chep@82-65-36-115.subs.proxad.net> has joined #yocto07:06
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Read error: Connection reset by peer)07:07
*** chep` is now known as chep07:07
*** zpfvo <zpfvo!~fvo@i59F5CCD4.versanet.de> has joined #yocto07:09
*** mckoan|away is now known as mckoan07:09
mckoangood morning07:10
*** frieder <frieder!~frieder@i577B934D.versanet.de> has joined #yocto07:11
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has joined #yocto07:14
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 246 seconds)07:14
*** nemik <nemik!~nemik@76.74.126.42> has joined #yocto07:14
*** zpfvo <zpfvo!~fvo@i59F5CCD4.versanet.de> has quit IRC (Ping timeout: 240 seconds)07:22
*** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 240 seconds)07:23
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto07:24
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto07:28
*** krissmaster <krissmaster!~kriss@213.239.83.90> has joined #yocto07:31
*** jclsn <jclsn!~jclsn@2a04:4540:6511:2500:2ce:39ff:fecf:efcd> has joined #yocto07:34
jclsnMorning guys07:34
jclsnDoes anyone here have experience with Layerscape secure boot? Still having issues07:35
*** zpfvo <zpfvo!~fvo@i59F5CCD4.versanet.de> has joined #yocto07:37
mckoanjclsn: actually not, only (A)HAB. Are you sure is a Yocto related issue?07:40
jclsnmckoan: Well, I don't understand what the recipe is doing fully07:42
jclsnhttps://github.com/Freescale/meta-freescale/blob/hardknott/recipes-bsp/atf/qoriq-atf_1.5.bb07:43
jclsnIt checks for some keys here https://github.com/Freescale/meta-freescale/blob/f0be684f01b53482cb43e016a5c5c1faf3ae448e/recipes-bsp/atf/qoriq-atf_1.5.bb#L7607:43
jclsnIt is checked if they are in the work directory, but I don't understand how I would provide my own keys07:44
jclsnI mean I wouldn't want the recipe to generate new keys every time if I have several boards07:44
jclsnAh maybe I could do a do_compile:prepend() and cp the keys to that location07:45
*** zpfvo <zpfvo!~fvo@i59F5CCD4.versanet.de> has quit IRC (Ping timeout: 265 seconds)07:56
*** bps2 <bps2!~bps@193.89.194.60> has joined #yocto07:58
*** zpfvo <zpfvo!~fvo@i59F5CD63.versanet.de> has joined #yocto08:10
jboHey guys, how exactly can I find out which DTS is ultimately being used?08:30
rburtonpaulg: yes that's target gcc and almost certainly because you have ptest enabled and elfutils in your build.  see my "why is my build so slow?!" presentation :) Turn off ptest if you don't use it.  Personally, I just turn ptest off for elfutils :)08:33
*** d-s-e <d-s-e!~d.s.e@i59F7CC72.versanet.de> has joined #yocto08:37
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto09:11
mckoanjbo: in your machine file there is KERNEL_DEVICETREE variable, then the bootloader have to know what to do09:24
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Ping timeout: 240 seconds)09:26
*** zpfvo <zpfvo!~fvo@i59F5CD63.versanet.de> has quit IRC (Ping timeout: 240 seconds)09:27
jbothanks!09:27
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 248 seconds)09:28
jboI'm trying to include GPM (general purpose mouse) in my image. I added "gpm" to my IMAGE_INSTALL:append. However, bitbake complains that nothing provides 'gpm'.09:34
jboI found this recipie: https://git.congatec.com/yocto/meta-openembedded/-/tree/b45a192ab7e337c7735ba57efadc1bdfedb37079/meta-oe/recipes-support/gpm09:34
jbobut clearly that is not working out for me. what am I missing/not-understanding?09:34
mckoanjbo: do you have  meta-openembedded09:39
mckoanmeta-oe09:39
mckoanjbo: do you have  meta-openembedded/meta-oe in your bblayers.conf ?09:40
jbomckoan, aye - thanks for the tip! Added that layer and now it's compiling :)09:40
jbostill learning the basics...09:40
*** zpfvo <zpfvo!~fvo@i59F5CFFD.versanet.de> has joined #yocto09:41
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto09:42
jbohmm... still no mouse cursor in the terminal (displayed via the framebuffer) tho.09:44
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto09:50
*** d-s-e <d-s-e!~d.s.e@i59F7CC72.versanet.de> has quit IRC (Ping timeout: 248 seconds)10:00
*** starblue <starblue!~juergen@dslb-094-220-115-218.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 264 seconds)10:03
*** starblue <starblue!~juergen@dslb-094-220-115-218.094.220.pools.vodafone-ip.de> has joined #yocto10:05
rburtonjbo: that's an incredibly old meta-oe, use https://git.openembedded.org/meta-openembedded/10:06
rburtonpro tip: layers.openembedded.org to find recipes10:06
*** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has joined #yocto10:06
jborburton, just checked the git repo remote and the one you linked is indeed the one I'm using10:07
jboalso thanks for pointing at layers.openembedded.org! that is useful!10:07
jbocurrently trying all the different mouse types (-t parameter of gpm) but nothing works. always logging "Error in read()ing first: Invalid argument"  :<10:09
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 240 seconds)10:09
*** zpfvo <zpfvo!~fvo@i59F5CFFD.versanet.de> has quit IRC (Ping timeout: 265 seconds)10:09
jboevtest seems to indicate a working mouse tho.10:12
rburtondoes gpm even work with modern systems? I've not used it for literally decades, but I see the list of supported mouse types doesn't include "evdev"10:23
jboI've no idea - doesn't seem like it so far :D10:23
*** zpfvo <zpfvo!~fvo@i59F5CFE5.versanet.de> has joined #yocto10:25
jboI'm trying to make a demo with a minimal GUI which directly tapps the framebuffer (no X, no Wayland, ...) which overall works. but there's no mouse cursor :D10:25
jbois there a more modern replacement for gpm?10:26
rburtonyour minimal GUI should just use evdev and draw a pointer etc10:30
jbocan't argue with that10:37
rburtonbasically, use a proper toolkit :)10:37
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto10:47
*** seninha <seninha!~seninha@user/seninha> has joined #yocto10:57
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)10:58
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto10:58
*** kpo_ <kpo_!~kpo@156.17.147.30> has joined #yocto11:04
*** Thorn_ <Thorn_!~Thorn@164.158.114.89.rev.vodafone.pt> has joined #yocto11:06
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 246 seconds)11:06
*** camus <camus!~Instantbi@58.246.136.203> has joined #yocto11:16
*** zpfvo <zpfvo!~fvo@i59F5CFE5.versanet.de> has quit IRC (Ping timeout: 240 seconds)11:19
*** zpfvo <zpfvo!~fvo@i59F5CC44.versanet.de> has joined #yocto11:35
*** d-s-e <d-s-e!~d.s.e@i59F7CC72.versanet.de> has joined #yocto11:47
*** kaitsh <kaitsh!~kaitsh@user/kaitsh> has joined #yocto12:04
*** d-s-e <d-s-e!~d.s.e@i59F7CC72.versanet.de> has quit IRC (Ping timeout: 240 seconds)12:07
*** d-s-e <d-s-e!~d.s.e@dynamic-046-114-091-157.46.114.pool.telefonica.de> has joined #yocto12:22
*** Algotech <Algotech!~Algotech@2a01:e0a:5e0:29b0:211:32ff:fe75:6948> has quit IRC (Ping timeout: 265 seconds)12:41
*** Algotech <Algotech!~Algotech@2a01:e0a:5e0:29b0:211:32ff:fe75:6948> has joined #yocto12:42
*** krissmaster <krissmaster!~kriss@213.239.83.90> has quit IRC (Remote host closed the connection)12:42
jboso far I have been using existing machine configurations for a dev-kit despite having custom hardware. I think it's time to create a custom machine config. I'm looking at the corresponding documentaiton right now. However, I'm not yet in the clear as to whether I can start by just declaring the minimal stuff required and then include/reference/inherit the existing dev-kit machine config?12:52
rburtonthe easiest thing would likely be to make a minimal one and then adds bits as you need them.  it depends on the bsp as to how modular they made it...12:53
jbothis is the one I've been using so far: https://git.toradex.com/cgit/meta-toradex-nxp.git/tree/conf/machine/verdin-imx8mm.conf12:55
jboalthough I guess in this case I just keep using that as that is for a SoM. For another project it might make more sense as there the machine config in use is for a particular EVK rather than just the SOM.12:56
jboin case of the imx8mm I'd just like to drop out all the wifi & bluetooth stuff12:57
rburtonif the bsp is designed right, just drop those from DISTRO_FEATURES12:58
jboalright, thanks for the hint. I'll look into DISTRO_FEATURES. I haven't created a custom distro yet. Just using poky.12:59
rburtonif you're doing something serious and not just playing, make a new distro13:01
rburtonpoky is an example and for qa. i expect you don't want bluetooth, or vulkan, or NFC13:01
rburtonpoky has all of those turned on13:01
jbountil now I was playing around to familiarize myself with yocto. now I am starting to go serious.13:01
jboso I guess now is the time to look into creating a distro. scary13:02
rburtonits not :)13:02
jboI've only done stimple stuff like  IMAGE_INSTALL:append  so far. and custom kernel configs and custom DTS patches.13:02
jbohttps://docs.yoctoproject.org/dev/dev-manual/custom-distribution.html13:03
jbothat actually seems pretty similar to everything else so far :)13:03
rburtonhttps://github.com/rossburton/customdistro/blob/master/meta-custom/conf/distro/custom.conf <-- a trivial one is trivial13:04
jbooh :)13:04
jbohow does a distro relate to/with an image I'm  building via bitbake <image_name>? So far I played around by building core-image-minimal, core-image-base and core-image-weston. I assume that the image "consumes" the distro? i.e. I will still be able to build different distros?13:05
*** vladest <vladest!~Thunderbi@217.192.139.41> has quit IRC (Ping timeout: 240 seconds)13:05
rburtonyeah, distro is policy, you can change distros and still build the same images13:05
jboalright13:05
jboso the documentation I just linked mentions that the distro is selected in local.conf. However, that is in the build directory. I do not yet understand how one creates something that can actually be shared with other developers in a way that they don't have to manually add all the layers and making changes to local.conf.13:06
jbohow does that work? I would not want my collegues having to do the same work each time. what have I currently not seen yet? :D13:06
rburtonhttps://github.com/rossburton/customdistro most likely needs updating for latest releases but it's super trivial for your distro layer to provide its own local.conf template which sets the right distro13:07
rburtonlike how when you oe-init-build-env in a poky tree your local.conf says DISTRO=poky13:07
rburtonif you use oe-core+bitbake directly, you don't get that13:08
jboI see. And how would that work with regards of adding layers? Currently, I cloned all the repos, did the  oe-init-build-env  and then used bitbake-layers add-layer to add the custom layer(s). Can that be automated?13:08
*** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-33-70-53-64-242.dsl.bell.ca> has joined #yocto13:08
jboi.e. I had to add more layers than just my custom layer. can I somehow tell my custom layer that it "requires" other layers such as meta-arm etc?13:09
rburtonthere is basic tooling inside bitbake now, or use kas, or git submodules13:09
rburtonthat customdistro thing uses submodules13:09
rburtonfor our CI we use kas13:09
jbothat part I have done (via git submodules). but when creating the build directory the first time I still have to modify the build/conf/bblayers.conf13:10
rburtonhave a look at customdistro :) specifically https://github.com/rossburton/customdistro/tree/master/meta-custom/conf13:12
jboalright - plenty of stuff to dig into - thank you! :)13:13
rburtonbasically local.conf and bblayers.conf are generated at init time from templates. you can provide those templates.13:14
*** mckoan is now known as mckoan|away13:14
jbothose templates being *.sample?13:14
rburtonyes13:14
rburtonyou'll see them in poky's repo too13:14
jbohmm... why exactly are you shipping both  *.conf and *.conf.sample  if the "real" one is being generated from the sample?13:17
jbonever mind.13:17
jboadding the layers automatically worked :)13:21
jbopre-populating local.conf worked too! excellent! thank you for your help :)13:24
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto13:29
jboactualy... I mistakenly edited the local.conf.sample & bblayers.conf.sample in the poky directory - lol. I corrected the mistake. However, how do I tell   "source oe-init-build-env"  to use the stuff from my meta-custom to populate conf/  ?13:33
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto13:33
rburtoneasiest way is to provide your own setup instead of oe-init-build-env13:36
rburtonagain, see https://github.com/rossburton/customdistro, specifically custom-init-env13:36
paulgrburton, RP - I typically start with the oe-init autogen'd conf/local.conf and then mash on it from there.  I'm guessing so do a lot of people.13:37
rburtonyeah, and poky turns on a load of stuff for testing purposes13:37
paulgAnd if I'm getting screwed by ptests being enabled, I guess it comes from that.13:37
rburtonif build time is a bother _and_ you don't run them, definitely disable them. the extra deps are quite invasive in places.13:39
jborburton, thanks, I'll try to fix my setup/layout.13:40
paulgI will definitely look into it for the hideously slow/old junk at home.13:40
jbobasically what I did is having a project directory. in there I have several git submodules for the various meta-* layers as well as poky/  I assume that I don't want to have poky/  anymore but  customdistro/  instead.13:40
rburtonyes, you can ditch poky/ but you'll need to replace it with oe-core and bitbake13:41
RPpaulg: we enable ptests by default else we just get patches which break the all over the place but there is a cost to it13:43
jboI've been doing this all wrong - thanks for showing me the way!13:43
jbowhen I started with yocto I was under the assumption that poky IS yocto *facepalm*13:45
paulgjbo, don't feel bad - there is definitely room for improvement in the communication dep't around poky/yocto/oe and the roles of each.13:46
jbooh, not feeling bad - also not blaming the docs. just the usual stuff when embarking with a completely new environment/ecosystem13:47
jboso looking at my previous bitbake output it seems to use version 2.0.0.  However, now that I will include bitbake as a git submodule, I see that there is a 2.4 branch - should I be using that instead?13:47
Entei[m]Does TUNE_CCARGS  unconditionally apply to all recipes being baked?13:48
rburtonEntei[m]: following variable references in bitbake.conf it ends up in CC, so you'd certainly hope so13:50
rburtonjbo: https://wiki.yoctoproject.org/wiki/Releases tells you what bitbake to use for what oe-core release13:50
jboexcellent - thank you!13:50
jbonothing more fun than a version inter-dependency matrix :D13:51
*** agrue <agrue!~agrue@host-23-251-65-128.VALOLT4.epbfi.com> has quit IRC (Ping timeout: 268 seconds)13:51
*** agrue <agrue!~agrue@host-23-251-65-128.VALOLT4.epbfi.com> has joined #yocto13:53
*** odra_ <odra_!~odra@177.94.130.83> has quit IRC (Quit: Leaving)13:56
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto13:58
jbogiven that I already ran into the issue of assuming that poky is yocto, let's better ask now: what exactly is "kirkstone"? Is that a particular yocto version/release?14:02
qschulzjbo: it's the release name for the 4.0.x branch of Yocto/OpenEmbedded-Core14:02
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)14:03
jbothat I understand. but what does it "consist of"? what does it "include"? for example, poky is unrelated to the yocto/oe-core release?14:03
*** d-s-e <d-s-e!~d.s.e@dynamic-046-114-091-157.46.114.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)14:04
*** d-s-e <d-s-e!~d.s.e@i59F7C274.versanet.de> has joined #yocto14:05
qschulzthat's probably a task for LetoThe2nd so I won't say wrong things14:05
qschulzpoky is a git repo that contains openembedded-core, bitbake and the yocto-docs git repository into one14:06
qschulzit's also the name of a distribution that is used for buildbots to check that things are still compiling well14:06
jbobased on that statement and the helpful resources that rburton linked earlier I assume that anybody doing something seirous would not use poky at all - is that correct?14:07
tomzy_0[m]Hello, how to work with Pseudo Abort errors? https://wiki.yoctoproject.org/wiki/Pseudo_Abort IIUC they may happened when something is deleting a file from WORKDIR of given recipe outside of that recipe context, so when we rebuild that recipe the Pseudo Abort may happen?14:07
qschulzjbo: that's what's recommended indeed, not everyone follows this advice though :)14:08
jboheh :)14:08
jboonce my work is done somebody has to get all of this thorugh several audits, FDA approval etc so I assume I safe those guys downstream a lot of headaches by doing things properly from the get-go of the prototyping phase.14:09
jboat least now I have learned to just have a look at the poky files to figure out how things are supposed to come together - that is plenty helpful!14:14
*** jetm <jetm!~quassel@177.93.3.234> has joined #yocto14:28
dwagenkHello. Does anyone have a good idea for the transistion psplash -> weston -> application ? I'm in a kirkstone based project using systemd as init manager.14:36
dwagenkpsplash-systemd explicitely sends a "QUIT" command to psplash once systemd reports a progress of 100%. But it terminates long before that, once weston starts loading.14:38
JPEWdwagenk: We run weston as a socket-activated service with the fullscreen shell (kiosk shell would work also) in systemd; this means that the splash screen stays up until our main application opens the socket to talk to weston, at which point system starts up weston14:38
JPEWThis minimize the amount of blank screen time between the splash screen and our application14:39
JPEWIIRC I upstreamed support for this to kirkstone.....14:39
dwagenksimilar setup here, the application triggers weston through teh socket, the weston.service unit is not enabled, so it only gets started through the socket.14:40
dwagenkI can try switching weston-shells around (currently it's the default desktop-shell) and see if it improves the situation.14:40
JPEWYa, fullscreen shell works well, but your application has to have special handling to deal with it. kiosk shell is the more modern replacement; it has the same idea (run a single application full screen), but looks more like a desktop shell so applications don't need special handling to use it14:41
dwagenkthe screen-blank time after the splashscreen disappears is longer than the duration of the splashscreen being shown on screen (I haven't done any initramfs or other optimizations yet to show it earlier).14:42
JPEWAh14:42
JPEWWe throw up the splash screen in the boot loader14:42
jbohmm... now that I fixed my overal yocto layout/structure bitbake cannot fetch something from toradex:14:43
jbo Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://git.toradex.com/linux-toradex.git;protocol=https;branch=toradex_5.15-2.1.x-imx;name=machine')14:43
jbohow do I investigate this?14:43
jbois that name=machine in there even legit?14:43
JPEWjbo: That just gives it a name for bitbake to use; it shouldn't affect the actual fetch IIRC14:44
*** d-s-e <d-s-e!~d.s.e@i59F7C274.versanet.de> has quit IRC (Ping timeout: 240 seconds)14:44
*** d-s-e <d-s-e!~d.s.e@i59F7C341.versanet.de> has joined #yocto14:44
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)14:44
JPEWjob: i.e. if you have multiple git repos in SRC_URI, you need to distinguish them14:44
dwagenkOn a different system (dunfell + sysVinit) I've used a weston + desktop-shell + application setup before. It was far easier there, since weston was started on a different tty via the openvt command in the weston-launch script. Removing the --switch argument from that script led to weston starting & preloading on an inactive VT. once the application signaled it was ready I could just run chvt to switch to the tty with weston and the application.14:45
jboJPEW, well, all I did was adding the  meta-toradex-*  layers as git submodules. I haven't touched anything INSIDE of those layers.14:45
dwagenkI'm trying to get a similarly smooth transition on the more modern stack, but it seems the weston.service and/or systemd-logind don't have a way to start weston on a VT in the background.14:46
JPEWdwagenk: Ya, I'm not sure14:46
dwagenkI'll try if using the fullscreen or kiosk shell bring notable improvements.14:47
dwagenkJPEW: thanks for teh help!14:47
JPEWdwagenk: np14:47
*** jetm <jetm!~quassel@177.93.3.234> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)14:48
JPEWdwagenk: If you figure it out, I'd be curious to know14:49
*** jetm <jetm!~quassel@177.93.3.234> has joined #yocto14:49
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)14:53
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto14:53
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)15:08
jboJPEW, I just re-ran the build command a couple of times and now it seems fine. not sure whether it was infrastructure problems on Toradex's sinde15:08
*** d-s-e <d-s-e!~d.s.e@i59F7C341.versanet.de> has quit IRC (Quit: Konversation terminated!)15:13
*** kpo_ <kpo_!~kpo@156.17.147.30> has quit IRC (Ping timeout: 248 seconds)15:19
*** bps2 <bps2!~bps@193.89.194.60> has quit IRC (Ping timeout: 268 seconds)15:21
tgamblinJPEW: would you mind replying to https://bugzilla.yoctoproject.org/show_bug.cgi?id=14890 (if you can answer Louis' question)?15:30
khemabelloni: Pick top 5 patches from https://git.yoctoproject.org/poky-contrib/log/?h=yoe/mut15:39
abellonikhem: ack, will do15:40
khemThey are same only that they have been rebased on top of abelloni/master-next15:40
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)15:40
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto15:41
*** goliath <goliath!~goliath@user/goliath> has joined #yocto15:44
jbohow do I correctly add to DISTRO_FEATURES? is it with  +=  or with DISTRO_FEATURES:append  ?15:44
*** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 268 seconds)15:45
rburtonjbo: if its _your_ distro then = :)15:50
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Quit: Bye)15:50
rburtonotherwise i'd use append as iirc poky does ?=15:50
jboaye. and when I want to have DISTOR_FEATURES depending on the image that I'm building? can I do something like   DISTRO_FEATURES:appaned:core-image-base = ""  or is that not how it works?15:50
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 248 seconds)15:52
*** tgamblin <tgamblin!~tgamblin@d72-39-239-122.home1.cgocable.net> has quit IRC (Remote host closed the connection)15:52
rburtonno15:52
rburton(that's not how it works)15:52
*** jetm <jetm!~quassel@177.93.3.234> has quit IRC (Ping timeout: 240 seconds)15:53
*** jetm <jetm!~quassel@177.93.3.234> has joined #yocto15:54
khemDISTRO overarches on IMAGE iow you build images based on distro15:57
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto15:57
jboaye, thanks!15:57
jbomanaged to have a bootable/runnable image with a custom distro :)15:58
jbothanks for all your help & patience guys - it's greatly appreciated!15:58
*** tgamblin <tgamblin!~tgamblin@d72-39-239-122.home1.cgocable.net> has joined #yocto15:59
*** Thorn_ <Thorn_!~Thorn@164.158.114.89.rev.vodafone.pt> has quit IRC (Ping timeout: 240 seconds)16:03
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto16:05
*** bps2 <bps2!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto16:09
*** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has quit IRC (Ping timeout: 248 seconds)16:09
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)16:14
*** bps2 <bps2!~bps@80.71.142.18.ipv4.parknet.dk> has quit IRC (Ping timeout: 248 seconds)16:19
*** zpfvo <zpfvo!~fvo@i59F5CC44.versanet.de> has quit IRC (Ping timeout: 240 seconds)16:27
*** starblue <starblue!~juergen@dslb-094-220-115-218.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 240 seconds)16:34
*** starblue <starblue!~juergen@dslb-094-221-185-245.094.221.pools.vodafone-ip.de> has joined #yocto16:35
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 248 seconds)16:37
*** kpo_ <kpo_!~kpo@user-5-173-248-163.play-internet.pl> has joined #yocto16:42
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds)16:44
*** kpo_ <kpo_!~kpo@user-5-173-248-163.play-internet.pl> has quit IRC (Ping timeout: 240 seconds)16:52
jetmPage https://www.yoctoproject.org/irc/ says "Sorry, but the page you were trying to view does not exist."17:00
*** kiwi_29_[m] <kiwi_29_[m]!~msgboardp@2001:470:69fc:105::1:6699> has joined #yocto17:05
*** duncan^ <duncan^!~duncan@nat-server.ehlab.uk> has joined #yocto17:06
duncan^I have EXTRA_USERS_PARAMS set up, which sets a password for root. How do I ensure that any changes to that password end up in the final rootfs? Is there a recipe/step shorthand for bitbake which will update this and produce a new image?17:07
duncan^A related question would be, is there an ideal way to rebuild a package and ensure inclusion in a new, final image?17:09
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has quit IRC (Ping timeout: 240 seconds)17:13
*** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto17:15
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has joined #yocto17:15
*** kpo_ <kpo_!~kpo@031011130025.dynamic-3-poz-k-1-0-0.vectranet.pl> has joined #yocto17:19
*** kpo_ <kpo_!~kpo@031011130025.dynamic-3-poz-k-1-0-0.vectranet.pl> has quit IRC (Ping timeout: 248 seconds)17:31
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has quit IRC (Ping timeout: 265 seconds)17:39
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)17:44
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Remote host closed the connection)18:00
rburtonIf you changed a recipe and that recipe produces a package that is in your image,  bitbaking the image will rebuild that recipe and then the image18:16
*** bryanb <bryanb!b5a314b1c0@2604:bf00:561:2000::106f> has quit IRC (Remote host closed the connection)18:28
*** tleb <tleb!6dbdd9ebc9@2604:bf00:561:2000::10cf> has quit IRC (Remote host closed the connection)18:28
*** bryanb <bryanb!b5a314b1c0@2604:bf00:561:2000::106f> has joined #yocto18:30
*** tleb <tleb!6dbdd9ebc9@2604:bf00:561:2000::10cf> has joined #yocto18:31
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)18:40
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto18:41
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has joined #yocto18:51
*** odra <odra!~odra@2804:431:c7e0:b9a0:b26f:55ae:ebb6:54ba> has quit IRC (Client Quit)18:54
abelloniRP: khem: libahci stil fails: https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/5917/steps/13/logs/stdio19:08
abellonimingw still fails too: winuser.h: No such file or directory19:14
*** u4ia <u4ia!u4iaaa@tilde.club> has quit IRC (Quit: WeeChat 3.8)19:17
*** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 264 seconds)19:18
*** kaitsh <kaitsh!~kaitsh@user/kaitsh> has quit IRC (Quit: WeeChat 3.7.1)19:20
*** frieder <frieder!~frieder@i577B934D.versanet.de> has quit IRC (Remote host closed the connection)19:33
duncan^rburton: thanks.19:35
*** BWhitten <BWhitten!~BWhitten@243.224.143.150.dyn.plus.net> has joined #yocto19:38
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)20:03
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto20:04
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has joined #yocto20:04
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)20:05
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Quit: Haxxa flies away.)20:15
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto20:18
jbois there some high-level guide on how to get started with creating a custom distro? I already set everything up to "have" a custom distro thanks to rburton but I kind of lack some guidance on where to go from here. i.e. how do I figure out what goes into a distro, what I might want, what I might not want etc?20:28
*** florian_kc <florian_kc!~florian@dynamic-093-132-051-174.93.132.pool.telefonica.de> has joined #yocto20:28
*** BWhitten <BWhitten!~BWhitten@243.224.143.150.dyn.plus.net> has quit IRC (Ping timeout: 264 seconds)20:28
*** seninha <seninha!~seninha@user/seninha> has joined #yocto20:38
*** BWhitten <BWhitten!~BWhitten@243.224.143.150.dyn.plus.net> has joined #yocto20:40
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Ping timeout: 246 seconds)21:22
*** Guest68 <Guest68!~Guest68@2001:420:30a:4e05:893a:833e:f1e4:2a4e> has joined #yocto21:24
*** Guest68 <Guest68!~Guest68@2001:420:30a:4e05:893a:833e:f1e4:2a4e> has quit IRC (Client Quit)21:24
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto21:36
*** gsalazar <gsalazar!~gsalazar@139.0.166.178.rev.vodafone.pt> has quit IRC (Ping timeout: 256 seconds)21:38
*** BWhitten <BWhitten!~BWhitten@243.224.143.150.dyn.plus.net> has quit IRC (Ping timeout: 268 seconds)21:49
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 268 seconds)21:59
*** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-33-70-53-64-242.dsl.bell.ca> has quit IRC (Quit: Konversation terminated!)22:00
khemabelloni: zeddii  hmm it uses 5.15 kernel, we need to backport https://github.com/torvalds/linux/commit/f07788079f515ca4a681c5f595bdad19cfbd7b1d22:15
khemand we also need to backport - https://github.com/torvalds/linux/commit/e6a71160cc145e18ab45195abf89884112e02dfb22:22
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Ping timeout: 240 seconds)22:23
*** florian_kc <florian_kc!~florian@dynamic-093-132-051-174.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 265 seconds)22:33
khemabelloni: can you point to AB logs for mingw issue ?22:33
abellonihttps://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/7183/steps/12/logs/stdio22:33
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Quit: Quit)22:41
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has quit IRC (Quit: Lost terminal)22:42
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has joined #yocto22:42
*** Net147 <Net147!~Net147@167-179-157-192.a7b39d.syd.nbn.aussiebb.net> has joined #yocto22:43
*** bps2 <bps2!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto22:46
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has quit IRC (Quit: Lost terminal)22:49
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has joined #yocto22:49
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has quit IRC (Client Quit)22:54
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has joined #yocto22:54
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has quit IRC (Client Quit)22:55
*** otavio <otavio!~otavio@201-66-236-34.user3p.brasiltelecom.net.br> has joined #yocto22:55
khemthx23:05
*** bps2 <bps2!~bps@80.71.142.18.ipv4.parknet.dk> has quit IRC (Ping timeout: 240 seconds)23:31
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto23:37
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto23:43

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