Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
rob_w has joined #yocto
Kubu_work has joined #yocto
Chaser has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
rfuentess has joined #yocto
zpfvo has joined #yocto
mckoan|away is now known as mckoan
enok has joined #yocto
xmn has quit [Ping timeout: 276 seconds]
davidinux has quit [Ping timeout: 244 seconds]
davidinux has joined #yocto
enok has quit [Quit: enok]
frieder has joined #yocto
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
Guest66 has quit [Quit: Client closed]
Chaser has joined #yocto
mvlad has joined #yocto
guest92 has joined #yocto
steelswords94 has quit [Read error: Connection reset by peer]
steelswords94 has joined #yocto
Daanct12 has joined #yocto
Daanct12 has quit [Client Quit]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
Daanct12 has joined #yocto
ys has joined #yocto
rob_w has quit [Ping timeout: 255 seconds]
ys has quit [Quit: Client closed]
alperak has joined #yocto
ys has joined #yocto
wojci has joined #yocto
<wojci>
A bit off topic .. Is it just me or is Labgrid documentation very hard to understand? Anyone uses Labgrid for testing Yocto on real HW that could answer some questions?
<rburton>
the problem is that there's so many use cases for labgrid. i agree the docs are a little terse :)
<hnez>
wojci: I am the person in the video rburton has linked to. But there should also be other Pengutronix/Labgrid people around here. Asking questions in #labgrid sounds like a good idea though.
<hnez>
wojci: We have recently published the labgrid/pytest testsuite for our LXA TAC hardware (which is Yocto based): https://github.com/linux-automation/labgrid-lxatac that may be useful to you as a real-life example
chrissi^|lxa has joined #yocto
<rburton>
oh that git repo looks very interesting!
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alimon has joined #yocto
ys has quit [Quit: Client closed]
wojci_ is now known as wojci
Daanct12 has quit [Quit: WeeChat 4.4.2]
rob_w has joined #yocto
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
Xagen has joined #yocto
<mcfrisk_>
RP: is there a problem with the uki related patches in master-next?
<rburton>
mcfrisk_: i suspect they made a broken image for me last week. i'll replicate now :)
rob_w has quit [Remote host closed the connection]
<RP>
mcfrisk_: rburton told me there was an issue but hasn't provided details yet ;-)
<mcfrisk_>
ok, I'll wait for the details too :)
gvmeson has quit [Quit: Konversation terminated!]
tlwoerner has joined #yocto
aduskett has joined #yocto
<aduskett>
Hello! Is it possible to have a kernel module recipe install multiple modules onto the root file system? I currently have a recipe that builds four modules, but only the one matching the name of the recipe makes it onto the file system. To be clear, all four .ko files show up in the tmp-glibc/work/${machine_name}/kernel-module-${package_name}/git-r0/image/lib/modules/${KERNEL_VERSION}/kernel/drivers/ directory, but only one module
<aduskett>
makes it to tmp-glibc/work/${MACHINE_NAME}/image/1.0-r0/rootfs/lib/modules/${KERNEL_VERSION}/kernel/drivers/
xmn has joined #yocto
<mcfrisk_>
aduskett: kernel modules are split into multiple binary packages by default. maybe your recipe builds more than one binary package so all of the would need to be installed to rootfs
<aduskett>
mcfrisk_: yes, the recipe builds four kernel modules from a single source directoy
<aduskett>
directory*
<rburton>
he means the modules would be split into separate _packages_
<aduskett>
Basically, I have kernel-module-metis_git.bb which builds axl-pcie-reset.ko, dmabuf-triton-exporter.ko, dmabuf-triton-importer.ko, and metis.ko in the source directory, but only metis.ko makes it to the rootfs
<aduskett>
rburton: bleh, but why would I need to make four separate packages if one package can build all four .ko files at once?
<rburton>
the options: 1) all kernel modules are always installed. 2) kernel module packaging has to be hand-written and maintained in the kernel recipe 3) automatically split module-per-package and let dependencies do the right thing
<aduskett>
oof, fair enough I guess
gvmeson is now known as vmeson
<rburton>
aduskett: feel free to add RDEPENDS in your recipe to pull them in at once if they're basically all needed at once
<aduskett>
rburton: Thank you for the help, it is much appreciated. And yeah, they are all needed on the rootfs
<aduskett>
It's a clients makefile, so I am also patching this thing to work with cross-compiling
<aduskett>
I guess I can make a base level .inc and inherit 99% of everything yeah?
<rburton>
to do what?
<rburton>
sounds like you've one recipe that builds four kernel modules so will generate four packages
<rburton>
that's fine
<aduskett>
yes, using one makefile it builds four .ko files
<rburton>
either install them all explicitly, or add rdepends to the recipe so that installing one pulls the others in
<aduskett>
oh, I do install them explicitly
merit has quit [Read error: Connection reset by peer]
<aduskett>
or, at least I think I do?
<rburton>
run that oe-pkgdata-util command i posted and see what packages the recipe generates
<rburton>
check that is actually four kernel-module-* packages...
<rburton>
and if it is then you've the list of packages to install (or add rdepends)
<sofsal>
hi, i'm trying to add all necessary packages like gnupg, systemd-container, dbus, debootstrap, systemd as init manager, so I can use systemd-nspawn containers with my yocto image. but still the containers aren't working as they should, am I missing something?
<aduskett>
ooo, fancy. Unfortuantly, the client has these shitty modules that only build against 5.10
<aduskett>
Bleh
<mrybczyn>
aduskett some people try to do such a thing, but you need to add metadata to each kernel cve... IMO not worth the pain. Would be better to fix those out-of-tree modules and upstream them :)
<mrybczyn>
the kernel people did what they did, and one of the reasons was to force people to upgrade
<aduskett>
mrybczyn: you are preaching to the choir lol
mjm has joined #yocto
leon-anavi has quit [Quit: Leaving]
zpfvo has quit [Quit: Leaving.]
<mrybczyn>
aduskett I understand their reasons. Your customer has other reasons...
mrybczyn has quit [Quit: Client closed]
<aduskett>
lol
<aduskett>
I was going to say to him, the customer has bad reasons
<aduskett>
I agree with them 100%
florian has quit [Ping timeout: 276 seconds]
mrybczyn has joined #yocto
mckoan is now known as mckoan|away
mrybczyn has quit [Quit: Client closed]
Kubu_work has quit [Quit: Leaving.]
florian has joined #yocto
wicki4 is now known as wicki
nerdboy has quit [Ping timeout: 248 seconds]
Saur_Home28 has joined #yocto
Saur_Home73 has joined #yocto
Saur_Home27 has quit [Ping timeout: 256 seconds]
Saur_Home28 has quit [Ping timeout: 256 seconds]
v0n has quit [Quit: WeeChat 4.4.2]
nerdboy has joined #yocto
vvn has quit [Quit: WeeChat 4.4.2]
vvn has joined #yocto
v0n has joined #yocto
steelswords94 has quit [Read error: Connection reset by peer]
steelswords94 has joined #yocto
sofsal has quit [Quit: Client closed]
florian has quit [Ping timeout: 252 seconds]
DixitP has joined #yocto
v0n has quit [Quit: WeeChat 4.4.2]
goliath has joined #yocto
vvn has quit [Quit: WeeChat 4.4.2]
vvn has joined #yocto
v0n has joined #yocto
vvn has quit [Client Quit]
v0n has quit [Quit: WeeChat 4.4.2]
vvn has joined #yocto
dankm has quit [Remote host closed the connection]
steelswords94 has quit [Read error: Connection reset by peer]
steelswords94 has joined #yocto
PhoenixMage has quit [Ping timeout: 252 seconds]
PhoenixMage has joined #yocto
Kubu_work has joined #yocto
tangofoxtrot has quit [Remote host closed the connection]
tangofoxtrot has joined #yocto
DixitP has quit [Quit: Client closed]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
Kubu_work has quit [Quit: Leaving.]
alperak has quit [Quit: Connection closed for inactivity]
<frosteyes>
khem: FYI the latest version of samba in scarthgap meta-openembedded (4.19.8) seems to depend on pyldb-util >= 2.8.1, but latest libldb in scarthgap is 2.8.0. So it fails to configure.
jmd has quit [Remote host closed the connection]
enok has joined #yocto
<frosteyes>
samba 4.19.6-r0 seems to work
druppy has joined #yocto
chep has quit [Remote host closed the connection]
chep has joined #yocto
<khem>
frosteyes: should be already fixed with today's update from Armin to stable starthgap PR
<frosteyes>
khem: perfect :)
goliath has quit [Quit: SIGSEGV]
steelswords94 has quit [Read error: Connection reset by peer]
druppy has quit [Ping timeout: 265 seconds]
steelswords94 has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jmiehe has joined #yocto
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
enok has quit [Ping timeout: 276 seconds]
gspbirel56 has quit [Ping timeout: 252 seconds]
mvlad has quit [Remote host closed the connection]