_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 272 seconds]
Degi_ is now known as Degi
bl0x_ has joined #litex
bl0x has quit [Ping timeout: 260 seconds]
<MoeIcenowy> somlo: my linux-on-litex-openc906 does automatic DT generation with initrd into consideration
<MoeIcenowy> and for your initrd, do you use things like dracut?
<MoeIcenowy> this kind of things could generate a multi-section initramfs
lexano has quit [Ping timeout: 268 seconds]
lexano has joined #litex
<somlo> well, if I'm not mistaken, you calculate INITRD_END by adding the size of your initrd file to INITRD_START: https://github.com/Icenowy/linux-on-litex-openc906/blob/master/Makefile#L32
<somlo> the problem I'm running into is that linux doesn't like that, at least not when my initrd is simply a gzip-ed cpio archive (not the fancy multi-layer voodoo that dracut does)
<somlo> here: https://github.com/litex-hub/linux-on-litex-vexriscv/issues/248#issuecomment-1367489940 is what happens, and I can't explain the difference between what linux's initrd decompressor expects and the actual gzip-ed file size itself
<somlo> I vaguely recall it not liking the exact *dracut* initrd file size either, but I'll have a chance to test that again and confirm/deny later today :)
acathla has joined #litex
<tpb> Title: Notion – The all-in-one workspace for your notes, tasks, wikis, and databases. (at theacodes.notion.site)