04:01 <swalker> updated openwrt/upstream, https://sdwalker.github.io/uscan/index.html

11:32 <neggles> stintel: ppc64 assembly is haunted

14:28 <russell--> slh: it appear it was due to some local customization, /etc/board.d/02_network is doing some magic that i was undoing

21:55 <CodingMarco> Hi, the u-boot on the device for which I'm porting OpenWrt needs an LZMA compressed ramdisk for the ramdisk image to boot successfully. Can this be configured persistently somehow outside of .config?

22:10 <PaulFertser> CodingMarco: OpenWrt uses only linked in ramdisk only for "initramfs" images which run fully from RAM.

22:23 <CodingMarco> PaulFertser: The ramdisk image is needed for my device to initially install OpenWrt via sysupgrade. However, with the default config (eg. on the build server), a non-bootable image is generated. Only if I set TARGET_INITRAMFS_COMPRESSION_LZMA=y in menuconfig, the image is bootable.

22:27 <PaulFertser> CodingMarco: so that's compression for the whole kernel+initramfs

22:29 <PaulFertser> Or are you really loading initramfs separately?

22:29 <PaulFertser> Is it a FIT image?

22:29 <PaulFertser> Do you really need it with CONFIG_TARGET_ROOTFS_INITRAMFS_SEPARATE ?

22:59 <stintel> 23:59:33 up 3 days, 5:28, 0 users, load average: 325.90, 326.19, 325.89

22:59 <stintel> nice

22:59 <stintel> 324 upsmon processes

23:07 <CodingMarco> PaulFertser: I have never used CONFIG_TARGET_ROOTFS_INITRAMFS_SEPARATE before. I tested it right now, but it also doesn't make a difference.

23:08 <PaulFertser> CodingMarco: that's not my point. I do not understand how you're booting that initramfs image at all. With regular OpenWrt initramfs the bootloader doesn't see initramfs, it's linked inside the kernel image.

23:09 <CodingMarco> As far as I can see in include/kernel-defaults.mk, CONFIG_TARGET_INITRAMFS_COMPRESSION_LZMA only affects initramfs, not the kernel.

23:10 <dwfreed> okay, you're confusing terms here

23:10 <dwfreed> there's two different "initramfs"

23:10 <dwfreed> there's the actual kernel initramfs, and then there's the openwrt "initramfs" image

23:11 <CodingMarco> PaulFertser: Yes, this is also what wonders me. The bootloader is a u-boot weirdly modified by huawei to support a kind of dual boot, a custom upgrade image etc.

23:11 <dwfreed> it sounds like you need the openwrt image to be lzma

23:11 <CodingMarco> dwfreed: Ahh ok...

23:14 <CodingMarco> I don't understand it entirely, I can just see that enabling/disabling TARGET_INITRAMFS_COMPRESSION_LZMA in menuconfig seems to decide between a bootable and non-bootable image.

23:16 <CodingMarco> Does this have anything to do with defining "KERNEL := kernel-bin | append-dtb | lzma | uImage lzma" differently somehow in the device makefile section?