dl9pf changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: http://www.yoctoproject.org | Join the community: http://www.yoctoproject.org/community | Channel logs available at https://www.yoctoproject.org/irc/ and https://libera.irclog.whitequark.org/yocto/ | Having difficulty on the list, or with someone on the list? Contact YP community mgr Nicolas Dechesne (ndec)
falk0n[m] has quit [Remote host closed the connection]
berton[m] has quit [Read error: Connection reset by peer]
rostam98[m] has quit [Read error: Connection reset by peer]
jwillikers[m] has quit [Read error: Connection reset by peer]
michaelo[m] has quit [Remote host closed the connection]
xicopitz[m] has quit [Read error: Connection reset by peer]
timbert[m] has quit [Read error: Connection reset by peer]
nicolas[m]12 has quit [Read error: Connection reset by peer]
t_unix[m] has quit [Write error: Connection reset by peer]
jonesv[m] has quit [Read error: Connection reset by peer]
m1kr0[m] has quit [Read error: Connection reset by peer]
keepitsimplejim[ has quit [Read error: Connection reset by peer]
alex88[m] has quit [Read error: Connection reset by peer]
asus_986_gpu[m] has quit [Read error: Connection reset by peer]
TurtleCrazy[m] has quit [Read error: Connection reset by peer]
dwagenk has quit [Read error: Connection reset by peer]
jordemort has quit [Read error: Connection reset by peer]
Saur[m] has quit [Read error: Connection reset by peer]
Alban[m] has quit [Read error: Connection reset by peer]
AlessandroTaglia has quit [Read error: Connection reset by peer]
lexano[m] has quit [Read error: Connection reset by peer]
TrevorWoerner[m] has quit [Read error: Connection reset by peer]
Spectrejan[m] has quit [Read error: Connection reset by peer]
khem has quit [Read error: Connection reset by peer]
meck[m] has quit [Read error: Connection reset by peer]
ndec[m] has quit [Read error: Connection reset by peer]
JonasVautherin[m has quit [Read error: Connection reset by peer]
barath has quit [Write error: Connection reset by peer]
kayterina[m] has quit [Write error: Connection reset by peer]
hmw[m] has quit [Write error: Connection reset by peer]
rodrjassoccom[m] has quit [Read error: Connection reset by peer]
cody has quit [Read error: Connection reset by peer]
moto_timo[m] has quit [Remote host closed the connection]
Emantor[m] has quit [Remote host closed the connection]
PascalBach[m] has quit [Read error: Connection reset by peer]
lacouture[m] has quit [Read error: Connection reset by peer]
shoragan|m has quit [Read error: Connection reset by peer]
behanw[m] has quit [Read error: Connection reset by peer]
christophs[m] has quit [Read error: Connection reset by peer]
tokamak[m] has quit [Read error: Connection reset by peer]
fabatera[m] has quit [Write error: Connection reset by peer]
ejoerns[m] has quit [Read error: Connection reset by peer]
SnowBeast[m] has quit [Read error: Connection reset by peer]
shoragan[m] has quit [Write error: Connection reset by peer]
SamuelDolt[m] has quit [Write error: Connection reset by peer]
Pierre-jeanTexie has quit [Read error: Connection reset by peer]
jordemort has joined #yocto
rostam98[m] has joined #yocto
<rpcme> ok completely cleaned from scratch and all is good in the world
keepitsimplejim[ has joined #yocto
Spectrejan[m] has joined #yocto
Alban[m] has joined #yocto
meck[m] has joined #yocto
kayterina[m] has joined #yocto
Emantor[m] has joined #yocto
lexano[m] has joined #yocto
rodrjassoccom[m] has joined #yocto
Saur[m] has joined #yocto
khem has joined #yocto
shoragan[m] has joined #yocto
Pierre-jeanTexie has joined #yocto
cody has joined #yocto
shoragan|m has joined #yocto
alex88[m] has joined #yocto
AlessandroTaglia has joined #yocto
ejoerns[m] has joined #yocto
xicopitz[m] has joined #yocto
moto_timo[m] has joined #yocto
asus_986_gpu[m] has joined #yocto
dwagenk has joined #yocto
t_unix[m] has joined #yocto
berton[m] has joined #yocto
ndec[m] has joined #yocto
fabatera[m] has joined #yocto
hmw[m] has joined #yocto
SnowBeast[m] has joined #yocto
PascalBach[m] has joined #yocto
TurtleCrazy[m] has joined #yocto
falk0n[m] has joined #yocto
JonasVautherin[m has joined #yocto
lacouture[m] has joined #yocto
timbert[m] has joined #yocto
barath has joined #yocto
SamuelDolt[m] has joined #yocto
jwillikers[m] has joined #yocto
TrevorWoerner[m] has joined #yocto
jonesv[m] has joined #yocto
tokamak[m] has joined #yocto
christophs[m] has joined #yocto
m1kr0[m] has joined #yocto
behanw[m] has joined #yocto
michaelo[m] has joined #yocto
nicolas[m]12 has joined #yocto
Tokamak has quit [Ping timeout: 240 seconds]
prabhakarlad has quit [Quit: Client closed]
camus1 has joined #yocto
rpcme has quit [Ping timeout: 246 seconds]
fray_ is now known as fray
camus1 has quit [Ping timeout: 240 seconds]
sakoman has quit [Quit: Leaving.]
roussinm has quit [Ping timeout: 258 seconds]
boo has quit [Ping timeout: 276 seconds]
mvlad has quit [*.net *.split]
Lihis has quit [*.net *.split]
Shaun has quit [*.net *.split]
rburton has quit [*.net *.split]
gchamp has quit [*.net *.split]
awafaa has quit [*.net *.split]
hauke has quit [*.net *.split]
stkw0 has quit [*.net *.split]
Shaun_ has joined #yocto
mvlad has joined #yocto
gchamp has joined #yocto
awafaa has joined #yocto
stkw0 has joined #yocto
hauke has joined #yocto
Lihis_ has joined #yocto
rburton has joined #yocto
Lihis_ is now known as Lihis
rburton has quit [Changing host]
rburton has joined #yocto
goliath has joined #yocto
rob_w has joined #yocto
ant__ has quit [Remote host closed the connection]
vd has quit [Ping timeout: 246 seconds]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #yocto
bps has joined #yocto
zpfvo has joined #yocto
frieder has joined #yocto
rsalveti has quit [Quit: Connection closed for inactivity]
LetoThe2nd has joined #yocto
<LetoThe2nd> yo dudX
<mihai> yo
vmeson has quit [Ping timeout: 265 seconds]
goliath has quit [Quit: SIGSEGV]
vmeson has joined #yocto
bps has quit [Ping timeout: 240 seconds]
prabhakarlad has joined #yocto
<qschulz> o/
florian has joined #yocto
bps has joined #yocto
bps has joined #yocto
bps has quit [Changing host]
kpo has quit [Read error: Connection reset by peer]
leon-anavi has joined #yocto
goliath has joined #yocto
rein_er has joined #yocto
Bardon has quit [Ping timeout: 258 seconds]
leon-anavi has quit [Remote host closed the connection]
leon-anavi has joined #yocto
Guest97 has joined #yocto
<Guest97> Hi guys! Could some1 help me with a question regarding LTS-support? Am I right that yocto has a LTS support of 2 years and each 2 years a LTS-version?
<RP> Guest97: correct
<Guest97> Thanks
ykrons_ has joined #yocto
ykrons has quit [Ping timeout: 272 seconds]
florian_kc has joined #yocto
<RP> LetoThe2nd: heh, nobody is going to understand that here :)
<LetoThe2nd> RP: thats the best part of in jokes!
<LetoThe2nd> RP: OTOH, that essentially makes it a V-amp, right? https://www.behringer.com/product.html?modelCode=P0961
<qschulz> RP: michaelo: I sent a diff for the overrides patches from RP on the bitbake-devel ML yesterday evening. At least comment on the two FIXME FIXME comments there are in the diff before applying it. Also, once ok, do you want me to send it as a patch so it's easier to apply? (it can be squashed afterwards, I don't care :) )
<RP> qschulz: I have that on my list of things to look at! :)
<RP> qschulz: I'm wondering how the test currently works for example
<qschulz> RP: not urgent for me, just wanted to highlight it since it's an unusual way of using the ML IMO :)
rein_er has quit [Ping timeout: 246 seconds]
leon-anavi has quit [Quit: Leaving]
jmiehe1 has joined #yocto
jmiehe has quit [Ping timeout: 272 seconds]
jmiehe1 is now known as jmiehe
<wyre> qschulz, apparently this doesn't help me https://bpa.st/4UOQ 😞
<qschulz> wyre: it actually does
<qschulz> you have the MMIO address of the gpio controller
<wyre> MMIO address? 🤔
<qschulz> go into the device tree and look for the name of the gpio controller node
<wyre> you mean the 20ac000?
<qschulz> register base address
<qschulz> yes
<wyre> qschulz, what's the proper way to modify the device tree for an image?
<qschulz> why are you talking about modifying the device tree?
<wyre> so I just need to read it?
<wyre> I mean, are you talking about before building the image?
<qschulz> wyre: yes, you should be able to know which dtb you're booting, then you find the correct file declaring this controller by going through the includes etc...
<wyre> well, I know the file is called imx6ull-microgea-microdev.dtb
<qschulz> on NXP IIRC there is no surprise in GPIOs order or naming, so you probably don't need to read the driver to figure out the order (which is different for Amlogic for example)
<wyre> but that's a binary
<qschulz> wyre: you have the sources of the kernel so you have the dts :)
<qschulz> (kernel dts that is)
<wyre> qschulz, you mean inside build dir?
<wyre> I cannot locate any dts file in build dir with find ... apparently I have to use devshell https://www.oreilly.com/library/view/embedded-linux-development/9781788399210/6bfad1cc-252c-49c7-8142-f3d87aeed718.xhtml
leon-anavi has joined #yocto
<wyre> I can see the nodes are in imx6ul.dtsi file https://bpa.st/74LA
<wyre> but this doesn't say me much either 🤔
<qschulz> what's your question
<LetoThe2nd> qschulz: "are you drunk?" - "not as much as i should be"
<qschulz> you know the GPIO1 bank starts at index 0, because gpio1 is at address 209c000 in the device tree
<qschulz> gpios on i.MX chips are named GPIOx_IOy with x being the bank/gpiochip and y being the gpio number in the bank
<qschulz> so if you're looking for GPIO1_IO7, you know it's going to be gpio7 in sysfs
<wyre> qschulz, what about the GPIO4_IO14?
<wyre> all gpiochips has 32 gpio ports?
<qschulz> wyre: you can do the maths with what's printed when you do cat /sys/kernel/debug/gpio :)
<qschulz> gpio4: gpio@20a8000, the address is gpiochip3, whose gpios start at index 96. To that you add 14, which means 110
<qschulz> provided the GPIO index per bank starts at 0 (i.e. GPIO1_IO00) and not 1 (GPIO1_IO01)
<wyre> qschulz, but according /sys/kernel/debug/gpio all gpiochips have 32 gpios and ... I'm not sure of this
<wyre> because according the i.MX6 reference manual ... the GPIO4, for example has only 29 gpio pins
<wyre> or the GPIO2, for example, has 22 pins
* qschulz shrugs
<JaMa> RP: should IMAGE_TYPEDEP use : like IMAGE_CMD? It currently doesn't and it might be confusing as mentioned in review comment in https://github.com/advancedtelematic/meta-updater/pull/816
jwillikers has joined #yocto
<wyre> qschulz, and what are those that are listed as `gpio-2 ( |UMTS_EN ) out hi` in /sys/kernel/debug/gpio?
<RP> JaMa: it doesn't: meta/classes/image.bbclass: deps = (d.getVar('IMAGE_TYPEDEP_' + t) or "").split()
<RP> JaMa: I agree it is confusing and we may want to think about changing that
<JaMa> RP: yes, I know it doesn't now
<RP> JaMa: I think we should change that one
<RP> JaMa: do you want to patch it or should I try something?
<JaMa> please do, I've quite a headache after yesterday's 2nd shot
<JaMa> I'll update the meta-updater PR when done
<qschulz> wyre: GPIOs that are already requested by drivers that you cannot request from userspace
<qschulz> with the name with which they were requested (which might (and often does) not match the name of the GPIO in the datasheet)
<wyre> you mean that often does not match, right?
<qschulz> yes
<wyre> qschulz, well, apparently the 110 is already requested 😥 `gpio-110 ( |ETH_ALIM_EN ) out hi`
rein_er has joined #yocto
rein_er has left #yocto [#yocto]
rpcme has joined #yocto
<rpcme> I was looking at the buildbot errors for meta-aws and it seems like there is layer compat errors for meta-openembedded layers. Is there any ETA on when this will be fixed? Or has it already been fixed and just waiting for another build rev?
Acki has joined #yocto
<michaelo> Hi halstead . Any issue on the Autobuilder for the docs? I have a few new commits in "master", but they still don't show on the generated docs (https://docs.yoctoproject.org/).
davidinux has quit [Ping timeout: 250 seconds]
davidinux has joined #yocto
<mihai> rpcme: make sure you have all layers checked out with the same branch
<wyre> qschulz, are these requests by drivers also listed in the device tree?
dtometzki has quit [Quit: ZNC 1.8.2 - https://znc.in]
<rpcme> mihai: I don't think I have a choice about that, this is run by YP's buildbot, and I only put in the layer dependencies... not what branch I want to run on... https://autobuilder.yoctoproject.org/typhoon/#/builders/122
<qschulz> wyre: they usually are yes, but there's many ways to requests GPIOs
<rpcme> RP: Is this a bug in the patch I submitted a while back? Unfortunately ... as we had discussed ... there's not an easy way for me to test the configuration I submitted without setting up a whole server and everything
<qschulz> wyre: I would suggest grepping in the kernel for ETH_ALIM_EN
<qschulz> I'm pretty sure it has something to do with either the Ethernet controller or the Ethernet PHY :)
Acki has quit [Ping timeout: 246 seconds]
<wyre> there is a whole node for all gpio exports
<qschulz> then you can probably access it from userspace in /sys/class/gpio/gpio110 maybe?
<wyre> qschulz, I cannot I have an `sh: write error: Device or resource busy` when I try to do the `echo 110 > export`
<wyre> also you can see there some assignment for voltage regulators(?)
boo has joined #yocto
<qschulz> wyre: well yes, because a driver has already requested the gpio so you cannot export it from sysfs
<qschulz> I don't know what this gpio-export driver does
<qschulz> and where it exports it, if it's even modifiable from userspace
<RP> rpcme: which errors do you mean? Is this the current overrides transition?
Bardon has joined #yocto
<wyre> also ... this leads me to another question ... this device tree is apparently for Engicam's carrierboard (MicroDev) but since I have a custom carrier board ... I guess I should have to make a custom device tree ... but how can I build an image with this custom device tree? 🤔
<wyre> is this specified in the image recipe?
<wyre> should I have a specific machine conf file?
<qschulz> wyre: yes, new machine conf file since it's different hw. Yes, new device tree because new hw. Usually to be added in the kernel recipe/sources and compiled there
<rpcme> RP: it looks like the layer compat setting for those is still set at hardknott and not honister - so yes, related to the overrides transition. you can see the layers in meta-openembedded that are failing here due to layer compat issue https://autobuilder.yoctoproject.org/typhoon/#/builders/122
<rpcme> on master-next on meta-openembedded it looks OK
<rpcme> master-next is what I have been using for my own testing.
<RP> rpcme: we'll just have to wait for the updates to merge to master
<rpcme> RP: Ok cool. I'm good with that. Just wanted to make sure meta-aws or the buildbot config for meta-aws isn't causing the problem (at least... for now :).
<wyre> qschulz, but should I do a fork of the kernel source code? https://github.com/engicam-stable/linux-engicam-nxp or just with the dts file is enough?
<qschulz> wyre: you can add patches in recipes, there is not necessarily a need for forking projects built by Yocto
<qschulz> it all depends how many changes you'll do, at one point, it makes sense to fork
<wyre> qschulz, well, I guess I could include this conf file https://github.com/engicam-stable/meta-engicam-nxp/blob/dunfell-community-bsp/conf/machine/imx6ull-microgea.conf in a new one in my layer and override the KERNEL_DEVICETREE variable, however .. where will bitbake look for the correspondent dts files?
<wyre> I guess still in the kernel sources, right?
<wyre> maybe I could even override KERNEL_DEVICETREE in my image recipe ... but ... I would need to provide the dts file 🤔
argonautx has joined #yocto
rsalveti has joined #yocto
sakoman has joined #yocto
Xagen has quit [Quit: Textual IRC Client: www.textualapp.com]
rob_w has quit [Quit: Leaving]
vd has joined #yocto
<wyre> should I also patch the Makefile? https://stackoverflow.com/a/61618880/6723042
goliath has quit [Quit: SIGSEGV]
Bardon has quit [Ping timeout: 268 seconds]
_whitelogger has joined #yocto
<RP> smurray: that is great to hear, thanks! :)
<smurray> RP: the weston issue I mentioned is unrelated I reproduced it with poky from last week, so I need to work out what that is still
<smurray> oops, insert a comma in that somewhere
<LetoThe2nd> smurray: "RP: the weston issue I mentioned is unrelated I reproduced it with poky from last week, so I need to work out what that is still,"
<LetoThe2nd> smurray: glad i could help
<smurray> ;)
sakoman has quit [Ping timeout: 256 seconds]
Tokamak has joined #yocto
<halstead> michaelo: I'll look into it.
amitk has quit [Ping timeout: 276 seconds]
amitk has joined #yocto
frieder has quit [Remote host closed the connection]
<halstead> michaelo: Re-running the build seems to have solved the problem. I don't see an error in the previous build but maybe the connection broke mid-copy in a way that wasn't reported?
yates_work has quit [Remote host closed the connection]
<michaelo> halstead: yess, thanks it worked now!
<halstead> michaelo: If it happens again we can look at capturing exit codes better. Let me know.
<michaelo> halstead: ok, thanks for your support
goliath has joined #yocto
Bardon has quit [Ping timeout: 258 seconds]
zpfvo has quit [Remote host closed the connection]
argonautx has quit [Quit: Leaving]
Bardon has joined #yocto
goliath has quit [Quit: SIGSEGV]
vd has quit [Quit: Client closed]
vd has joined #yocto
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 258 seconds]
<michaelo> qschulz: hallo. Any plans for the docs updates for the new overrides syntax? Do you want to submit patches or shall I?
goliath has joined #yocto
aeroraptor has joined #yocto
LetoThe2nd has quit [Quit: Connection closed for inactivity]
dtometzki has joined #yocto
<aeroraptor> Hello everyone! I'm new to yocto but I think it'll be a good fit for a Pi project I have been working on. Does anyone have experience including their own config.txt in a build?
<aeroraptor> I have found this example but it feels very sloppy: https://raspberrypi.stackexchange.com/a/32159/130291
florian_kc has joined #yocto
jmiehe has quit [Quit: jmiehe]
Shaun_ is now known as Shaun
Xagen has joined #yocto
<Xagen> I have a toaster build that I'm doing. I build all of the dependencies individually to make sure they build. Then I try to build the image. It's seemingly not finding some of the packages as it says that there's `No match for argument <package>` for several packages. However, I know that they've built because I built them already. Any ideas why this might happen?
florian_kc has quit [Ping timeout: 258 seconds]
Guest8 has joined #yocto
Guest8 has quit [Client Quit]
florian_kc has joined #yocto
lexano has quit [Ping timeout: 250 seconds]
lexano has joined #yocto
goliath has quit [Quit: SIGSEGV]
<tlwoerner> RP: PREFERRED_VERSION_linux-yocto is also not an override (?)
<tlwoerner> it looks like PREFERRED_VERSION_linux-yocto:nanopi-m4-2gb = "5.10%" works but PREFERRED_VERSION:linux-yocto:nanopi-m4-2gb doesn't
<RP> tlwoerner: correct, PREFERRED_VERSION is not an override
<RP> well, the suffix to
<tlwoerner> is the list published somewhere? BBFILE_PATTERN, SRCREV_<name> (but not SRCREV_${PN}), IMAGE_TYPEDEP, PREFERRED_VERSION
goliath has joined #yocto
<RP> tlwoerner: The proposal is we update the migration guide
<RP> tlwoerner: you means SRCREV_pn-${PN} right?
<tlwoerner> RP: hmm there are a couple instances in meta-arm that don't have the _pn-
<RP> tlwoerner: right, but that isn't ${PN}
<RP> it is a name from the SRC_URI
<tlwoerner> ah good. i see what you're saying now. i'll update the meeting notes etc
<tlwoerner> zeddii: ping?
<smurray> JPEW: before I forget again, I needed this small tweak on top of your child process patch: https://paste.debian.net/1206481/
leon-anavi has quit [Quit: Leaving]
florian_kc has quit [Ping timeout: 258 seconds]
<RP> khem, vmeson: Not sure what to do with the ptest failures with glibc 2.34 (strace, valgrind, elfutils)
<RP> 2.34 patch is otherwise ready
dgriego has quit [Quit: Textual IRC Client: www.textualapp.com]
RP has quit [Ping timeout: 240 seconds]
goliath has quit [Quit: SIGSEGV]