[OpenWrt-Devel] [PATCH 0/2] [RFC] build: allow selective per device initramfs

Kristian Evensen kristian.evensen at gmail.com
Mon May 6 04:12:23 EDT 2019


Hi Petr,

On Sun, May 5, 2019 at 10:14 PM Petr Štetiar <ynezz at true.cz> wrote:
> I find it quite weird to demand any kind of compilation by the end-users, but
> I also find it quite wasteful to build initramfs images for all devices under
> particular target (lantiq/xrx200 and ramips/mt7620), just because one (or
> minority) of device needs this image.
>
> So I've looked at the possible solutions, and with the limited time on hand
> I've come up with the following patch series. I'm sure, that this is kind of a
> weird workaround, but I find it less obtrusive then building of initramfs
> images for all targets, with no apparent use.
>
> Essential solution would be something like image recipe for initramfs, but
> since it's quite complicated topic it would need a lot more time to fix it
> properly.
>
> So I'm wondering if such workaround to avoid building of unnecessary initramfs
> images would be acceptable, or until there's a proper solution, we should
> simply live with the `FEATURES += ramdisk` based "solution".

Thank you for sharing your patches. I had started implementing a
similar solution, but quickly abandoned my work when I saw the commits
in your staging tree. Even though I have no authority, I think your
solution is nice and it solves the problem at hand. I applied your
patches and modified mt7620 + the HDRM200 target accordingly, and as
expected I only get one initramfs image. I agree that building
initramfs for devices that do not need it is redundant (I see that
initramfs is built for all mt7621 targets for example), so I am very
much in favor of merging this series.

BR,
Kristian

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list