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)
creich_ has quit [Quit: Leaving]
creich has joined #yocto
qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
jpuhlman_ has joined #yocto
jpuhlman__ has quit [Ping timeout: 250 seconds]
sakoman has quit [Quit: Leaving.]
xmn has joined #yocto
sakoman has joined #yocto
Vonter has joined #yocto
sakoman has quit [Quit: Leaving.]
paulg has quit [Ping timeout: 258 seconds]
goliath has joined #yocto
grma has quit [*.net *.split]
Ch^W has quit [*.net *.split]
Ch^W has joined #yocto
marex_ has joined #yocto
marex has quit [*.net *.split]
florian has joined #yocto
<RP> nice, master failing with the rcu failure but at least clearly showing it in the logs
<RP> abelloni: we have another bootloader crash :/
<RP> zedd: could I trouble you to send out the 5.10 kernel bump patches please? Not sure either of us want me to upset the workflow :)
<ant_> RP: please consider backporting the 2 kernel/nopackages fixes to Hardknott and Gatesgarthm thx
<RP> ant_: gatesgarth is out of maintenance now
<RP> for hardknott, you need to ask the stable maintainer (Anuj), not me
<ant_> imho nobody will notice it :)
<RP> and they're not even in master or fully tested yet
<RP> ant_: you have no idea how often I hear that said and then something really badly breaks
* RP usually gets to keep all the pieces
<ant_> heh, and dunfell builds ok both kernels, I'd say we are done then
* ant_ hopes not having made RP adding new issues...
jonah1024 has joined #yocto
<ant_> RP: the kernel.bbclass did badly inflate in the years
<ant_> but if I am not wrong the whole *BUNDLE stuff could be removed
<RP> ant_: what makes you say that?
<ant_> with the commit adding KERNEL_PACKAGE_NAME
<ant_> KERNEL_DEPLOYSUBDIR ??= "${@ "" if (d.getVar("KERNEL_PACKAGE_NAME") == "kernel") else d.getVar("KERNEL_PACKAGE_NAME") }"
<ant_> you could build n kernels each in a subdir
<ant_> let me find the commit
<ant_> linux-kexecboot is cut down, this way allows you to have full kernel with modules
<ant_> afais you could build a kernel+initramfs as second kernel
<ant_> w/out the BUNDLE code
<ant_> just add to your other kernel recipe:
<ant_> INITRAMFS_IMAGE = "initramfs-foo-image"
<ant_> INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_image_complete"
<ant_> zedd, you could build linux-yocto and linux-yocto-tiny in one run
<ant_> and even a third linux-yocto-initramfs to provide an example
<ant_> RP: ofc you can add KERNEL_PACKAGE_NAME in the recipe, not only in local.conf as in the commit text
<ant_> I think this is a BIG added feature but was almost ignored
marex_ is now known as marex
xmn has quit [Quit: ZZZzzz…]
florian has quit [Ping timeout: 252 seconds]
florian has joined #yocto
camus has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 272 seconds]
camus1 is now known as camus
jonah1024 has quit [Quit: Connection closed for inactivity]
paulg has joined #yocto
xmn has joined #yocto
<RP> zedd: Thanks. I think there was a kernel_version uprev missing but I'll sqaush that in :)
<zedd> hmm. no, there shouldn't have been
<zedd> what do you think you are seeing ?
<RP> zedd: 5.10.43 -> 5.10.46 ?
<zedd> that's in the patches I sent.
<zedd> ah. I see.
<zedd> drop the series completely. that script misfired, and ran on the bbappend.
<zedd> it's complete garbage.
<RP> zedd: ah :/ I'd best stop that build too!
florian has quit [Ping timeout: 268 seconds]
<RP> zedd: the update for the main recipe is also there, just missing the kernel_version
<zedd> no. don't use any of them. I'll send a v2 later.
<RP> zedd: ok
goliath has quit [Quit: SIGSEGV]
warthog9 has quit [Remote host closed the connection]
warthog9 has joined #yocto
jonah1024 has joined #yocto
florian has joined #yocto
florian has quit [Ping timeout: 252 seconds]
<paulg> Good help is hard to find.
<marex> paulg: was it you who was working on the linux 5.10.y and co. backports for dunfell ?
<marex> I recall seeing such discussion before fosdem time here
<marex> also, unrelated -- is there some way to speed up yocto-check-layer in CI setting ? it takes about as long as the whole build for me, is there some trick to that ?
<marex> I basically want to make sure the layers dont start to pile up broken bbappends and such
<paulg> marex, I did the 4.8, 4.12, 4.18 and 5.2 updates; things shuffled around that I didn't need to do v5.8 and we get v5.10 "for free" as an LTS from gregKH's team.
<marex> paulg: so how does that work now ? I maintain my own repo with linux lts for dunfell (and u-boot too)
<marex> and mesa
<marex> paulg: I mean, the OE integration
<paulg> marex, zedd grabs the stable updates from gregKH's team directly ; the versions I mentioned above had been declared EOL by gregKH but we (yocto) needed ongoing maintenance a little longer.
<marex> paulg: I mostly care about 5.10.y anyway
<marex> paulg: is there a metalayer or something ?
<paulg> but as said above, zedd is taking those in directly within a few days of their release.
<marex> paulg: I see, thank you
<marex> paulg: so, yes, I know where to get the sources , I was asking whether there is some metalayer already
<marex> paulg: if not, I'll stick to my own, which does exactly what I need
<marex> it just seems like this is something that would be useful to others as well
<marex> and I was under the impression there was some ongoing work to put these updated recipes upstream
<paulg> you don't need any special anything if you just want vanilla v5.10.<latest> as zedd has that on v5.10/standard/base
<RP> marex: you can get a plain mainline kernel out of the linux-yocto recipes
<marex> RP: ah nice ... I must've missed it in oe-core/dunfell
<marex> hmmm ... no, I only see 5.4.y there
<RP> marex: sorry, I missed you were looking for this in dunfell
<marex> RP: yep :)
<RP> marex: I think denys is lookin at experimenting with that though, shouldn't be hard
<marex> RP: so far I rolled my own layer, see above, with u-boot/linux/mesa and I think I will soon add gstreamer 1.18.y
<marex> RP: I thought someone was looking into that too, but maybe it got nowhere
<paulg> ah okay - I suck at code names ; also didn't realize dumbell was v5.4-only...
<marex> paulg: well, I started adding version to the branch names because i was getting lost in it, hence the dunfell-3.1
<RP> paulg: we're getting a ton of "complaints" that the LTS has been stable ;-)
<paulg> so, no - AFAIK, I wasn't disucssing backporting the 5.10 recipe to releases that didnt have it by default - must have been someone else.
<paulg> that said, I would expect it to largely be a drop in and maybe check for updates that landed in recipes-kernel/linux/linux-yocto.inc since 5.10 was added?
<marex> RP: I wonder, would it be possible to put some of those updated recipes into contrib or something ?
<marex> and that's another thing I was wondering about -- why not use stock linux-stable , why keep this linux-yocto with patches ?
<RP> marex: sure, definitely possible. The TSC did also say they'd support the idea of mixin layers for exactly this kind of thing
sakoman has joined #yocto
<RP> marex: you can select either from linux-yocto and some of these patches you appear to hate actually let us do things like the qemu testing so they do kind of help ;-)
<marex> RP: I never said anything about hating
<marex> RP: they just seemed like something which needs to be constantly maintained
<marex> and something most boards dont really need
<marex> I wonder if those patches couldn't be isolated to the qemu machines then ?
<RP> marex: I'm going to get annoyed with this conversation so I'm just going to walk away from it
<RP> I'll leave with the question of whether you think we just make work for ourselves by doing it or whether there are actual reasons?
<marex> RP: I was curious about the reasons
<RP> marex: it has been discussed many times before. We should probably try and write it up somewhere
<marex> RP: hmmmm, that might be a good idea
<marex> RP: btw while you bring up testing, I have one more question about this yocto-check-layer
<marex> RP: it just takes too long, roughly the same time it takes to do my CI build with primed sstate cache, is there some trick to speeding it up?
<marex> I can imagine the OE CI does check the layers, right ?
<RP> marex: It should be equivalent to parsing the metadata a couple of times and it does do a build dry run
<marex> RP: thanks, lemme read through that
<marex> RP: so Test meta-oe YP Compatibility: Run cmds ... that takes 29 minutes ?
<RP> marex: correct, yes
<marex> that does seem a bit long, can anything be done about that ?
ant_ has quit [Remote host closed the connection]
ant has joined #yocto
ant is now known as Guest5263
Guest5263 has quit [Client Quit]
ant__ has joined #yocto
<RP> marex: possibly, not sure. It would need time spending on it
florian has joined #yocto
<RP> marex: meta-oe is an outlier since it runs the check on eash sub-layer
<ant__> RP: I sent a RFC about meta-oe and its layers. Khem is doing an outstanding work to maintain alltogether
<ant__> I think it still looks like to a matrioska, there iis much to improve
<ant__> we started to split out layers but I think we miss a 'project'
dev1990 has joined #yocto
davidinux1 has quit [Ping timeout: 244 seconds]
davidinux1 has joined #yocto
<marex> RP: well, running the yocto-check-layer in parallel for each layer seems to improve situation considerably
<marex> RP: compared to running it for all layers "sequentially"
florian has quit [Ping timeout: 268 seconds]
jonah1024 has quit [Quit: Connection closed for inactivity]
warthog9 has quit [Remote host closed the connection]
warthog9 has joined #yocto
florian has joined #yocto
camus has quit [Remote host closed the connection]
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
nerdboy_ has joined #yocto
florian has quit [Ping timeout: 268 seconds]
pidge_ has quit [Remote host closed the connection]
nerdboy has quit [Ping timeout: 256 seconds]
pidge_ has joined #yocto
florian has joined #yocto
georgem has joined #yocto
goliath has joined #yocto
Vonter has quit [Ping timeout: 268 seconds]
Vonter has joined #yocto
pidge has joined #yocto
pidge_ has quit [Read error: Connection reset by peer]
florian has quit [Ping timeout: 258 seconds]
florian has joined #yocto
goliath has quit [Quit: SIGSEGV]
florian has quit [Ping timeout: 268 seconds]
pidge has quit [Quit: Leaving]
BobPungartnik has joined #yocto
florian has joined #yocto
xmn has quit [Ping timeout: 265 seconds]
florian has quit [Ping timeout: 265 seconds]
BobPungartnik has quit [Quit: Leaving]
davidinux1 has quit [Ping timeout: 258 seconds]