vladest has quit [Remote host closed the connection]
vladest has joined #yocto
gsalazar has joined #yocto
LocutusOfBorg has quit [Quit: ZNC 1.8.2+deb3 - https://znc.in]
LocutusOfBorg has joined #yocto
<efeschiyan>
hey there folks, I am looking how to put a single firmware blob within the kernel but my attempts in whacking yocto to do what I want it do to seem to be failing. I found that only 2 people - derRichard and qschulz - obviously had the same idea as me, at least from what I can find from libera's chatlogs - https://libera.irclog.whitequark.org/yocto/search?q=CONFIG_FIRMWARE_EXTRA . is there a reasonable
<efeschiyan>
way to make the linux-firmware sysroot be available during a kernel compilation process so I could pick a single blob and add it to CONFIG_FIRMWARE_EXTRA ?
GillesM has left #yocto [Leaving]
leon-anavi has joined #yocto
dv_ has quit [Quit: WeeChat 3.0]
<derRichard>
efeschiyan: let me check
<mckoan>
efeschiyan: doesn't putting firmware blob within the kernel violate the GPLv2 ?
<derRichard>
depends on the license of the firmware blob...
<mckoan>
derRichard: usually FW has a specific license incompatible with GPLv2
alessioigor has joined #yocto
<derRichard>
mckoan: usually but not always. it depends on the firmware itself.
<derRichard>
and the firmware is not linked to the kernel (program). it is just part of the archive. like a zip file or a fit image...
<derRichard>
efeschiyan: just checked how i solved it.
<efeschiyan>
I tried task dependency in various steps but the SYSROOT_DIRS is probably is what I am looking for. I'll try it in a bit, much appreciated
Guest98 has quit [Quit: Client closed]
Guest98 has joined #yocto
louson has quit [Ping timeout: 264 seconds]
falk0n[m] has quit [Remote host closed the connection]
zpfvo has quit [Ping timeout: 244 seconds]
starblue has quit [Ping timeout: 250 seconds]
starblue has joined #yocto
zpfvo has joined #yocto
mckoan is now known as mckoan|away
falk0n[m] has joined #yocto
<efeschiyan>
derRichard: thanks mate. that seems to be only half of the story at least on my side, I thought I was going insane - the linux-firmware_20230404.bb has SYSROOT_DIRS_IGNORE += "${nonarch_base_libdir}/firmware" at the bottom which ruins the fun - from kirkstone onwards is there and before that it wasn't; I had to override/empty that in a bbappend. after that I slapped do_configure[depends] +=
<efeschiyan>
"linux-firmware:do_populate_sysroot"
<efeschiyan>
in the kernel bbappend I am building and that made it work
<derRichard>
efeschiyan: oh fun ahead when I upgrade ;-/
Guest98 has quit [Ping timeout: 246 seconds]
<efeschiyan>
yeah might save you some head banging. I was completely lost last week when I was trying to do that and finally decided to ask here
Guest98 has joined #yocto
<derRichard>
efeschiyan: yes, thanks a lot for letting me know!
Tokamak_ has quit [Quit: Tokamak_]
Guest98 has quit [Ping timeout: 246 seconds]
Guest98 has joined #yocto
Guest98 has quit [Quit: Ping timeout (120 seconds)]
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
dmoseley has joined #yocto
rob_w has quit [Quit: Leaving]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Schlumpf has quit [Quit: Client closed]
pgowda_ has quit [Quit: Connection closed for inactivity]
Guest98 has joined #yocto
xmn has quit [Quit: ZZZzzz…]
lexano has joined #yocto
sakoman has joined #yocto
<zelgomer>
"Error: TEMPLATECONF value (which is /path/to/my/top-build/conf) must point to meta-some-layer/conf/templates/template-name" <-- why?? why would i want to put my templates in a meta-layer instead of in my toplevel build dir, since that's what ties all of the layers together?
Bardon_ has joined #yocto
hcg has quit [Quit: Client closed]
Bardon has quit [Ping timeout: 246 seconds]
tgamblin has quit [Ping timeout: 244 seconds]
goliath has quit [Quit: SIGSEGV]
Guest98 has quit [Quit: Client closed]
<jonmason>
poky-tiny issue bisected to 6d5adecd028582bf548cfa47c3b0f9e76fbc2d1f "eudev: Add group sgx to eudev package"
<jonmason>
RP: I assume you want me to open a bug for this
rob_w has joined #yocto
<jonmason>
Also, I've found the 3 lines that are breaking qemuarm fb in 6.4 kernel
alessioigor has quit [Read error: Connection reset by peer]
<RP>
jonmason: I'm not sure which poky-tiny issue that is but yes please
<jonmason>
"qemuarm64 login: <<< run_serial(): command timed out after 120 seconds without output >>>"
<jonmason>
"WARNING: core-image-minimal-1.0-r0 do_testimage: Couldn't login into serial console as root using blank password"
<RP>
jonmason: how does a new group break that? :(
<jonmason>
RP: apparently. I bisected it to that patch and did a sanity/clean run (which I can do again without sstate if you want)
frieder has quit [Remote host closed the connection]
<zelgomer>
oh fuck this shit. fuck you guys for renaming a ton of variables because they contained the word white
<RP>
jonmason: I don't doubt it, I just wonder what is going on
<RP>
zelgomer: You clearly need to learn about impact of choice of language. I'm sure you'll work out a migration in the end.
<zelgomer>
RP: get your religion out of my engineering
<jonmason>
RP: I can take a look after I'm done with the qemuarm framebuffer issue. I'm out next week. So, not 100% I'll get to a conclusion before Friday
<RP>
jonmason: ok, np, thanks
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
goliath has joined #yocto
hpsy[m] has quit [Remote host closed the connection]
zpfvo has quit [Remote host closed the connection]
weepiie has quit [Remote host closed the connection]
rfuentess has quit [Remote host closed the connection]
florian_kc has joined #yocto
aardo has joined #yocto
ardo has quit [Ping timeout: 264 seconds]
gsalazar has quit [Ping timeout: 246 seconds]
dgriego has quit [Ping timeout: 244 seconds]
florian_kc has quit [Ping timeout: 246 seconds]
ChanServ has quit [shutting down]
dgriego has joined #yocto
ChanServ has joined #yocto
Guest67 has joined #yocto
<Guest67>
does anyone busybox truncate the permission name of the owner/group to 8 characters?
<Guest67>
for example, I have user/group created with 9 characters (abcdefghi : acbdefghi), but when viewing the permissions of the file, it's listed as (abcdefgh : abcdefgh):
<Guest67>
-rw-r--r-- 1 abcdefgh abcdefgh 7 Jul 24 14:19 test
<Guest67>
the /etc/passwd and /etc/group looks correct though
<DvorkinDmitry>
I have xxx machine. I need to create two more machines: xxx-X0, xxx-X1 to have all rules working (in my recipes) for xxx machine and if specified xxx-X0 - the rulle has been applied for machine xxx-X0 only together with the rules for xxx (base) machine. How to do that correctly?
mvlad has quit [Remote host closed the connection]
<zelgomer>
DvorkinDmitry: this is where MACHINEOVERRIDES can help you. xxx.conf can add MACHINEOVERRIDES =. "xxx:" and xxx-X0 can add MACHINEOVERRIDES =. "xxx-X0:xxx:". now in recipes you can use VARIABLE:xxx = "..." or VARIABLE:xxx:append = " ..." to apply to any xxx machine, and VARIABLE:xxx-X0:append = " ..." (etc.) to apply only to the xxx-X0 version.
<zelgomer>
DvorkinDmitry: in dunfell use an underscore instead of colon for override syntax-- VARIABLE_xxx_append
<zelgomer>
DvorkinDmitry: you might consider at least spending some time with the dunfell manual to look up MACHINEOVERRIDES or override syntax before abandoning a suggestion outright
Guest67 has quit [Quit: Client closed]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
amitk has quit [Ping timeout: 244 seconds]
<DvorkinDmitry>
zelgomer, thank you!
<DvorkinDmitry>
is it ok to use "-" in machine name? or I should better name it xxxX0, for example?
<zelgomer>
i think it's ok
schtobia has quit [Quit: Bye!]
schtobia has joined #yocto
tnovotny has joined #yocto
gsalazar has joined #yocto
beneth has joined #yocto
yannd has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
tnovotny has quit [Quit: Leaving]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
pbsds has joined #yocto
wooosaiiii has quit [Ping timeout: 245 seconds]
Net147 has quit [Ping timeout: 246 seconds]
florian_kc has joined #yocto
<adrianf>
DvorkinDmitry: If I remember correctly it is OK, but the MACHINE variable is usually part of the IMAGE_LINK_NAME where the - of the MACHINE name gets replaced by _. This can be misleading when dealing with artifacts later on. I try to avoid it because of that. But it's quite some time ago when I was debugging this on our CI infrastructure.
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has joined #yocto
gsalazar has quit [Ping timeout: 260 seconds]
eLmankku has quit [Remote host closed the connection]
mcfrisk has quit [Remote host closed the connection]