[PATCH] mvebu: cortexa9: fix missing wpad and iwinfo in images
mail at adrianschmutzler.de
Sun Feb 14 07:06:44 EST 2021
> -----Original Message-----
> From: openwrt-devel [mailto:openwrt-devel-bounces at lists.openwrt.org]
> On Behalf Of Petr Štetiar
> Sent: Sonntag, 14. Februar 2021 08:31
> To: Adrian Schmutzler <mail at adrianschmutzler.de>
> Cc: 'Tomasz Maciej Nowak' <tmn505 at gmail.com>; openwrt-
> devel at lists.openwrt.org; 'Klaus Kudielka' <klaus.kudielka at gmail.com>
> Subject: Re: [PATCH] mvebu: cortexa9: fix missing wpad and iwinfo in
> Adrian Schmutzler <mail at adrianschmutzler.de> [2021-02-13 15:49:17]:
> > > Seem like I need to prepare v2 as although I now have wpad/iwinfo in
> > > the image, I'm still missing ath10 and ath9k wireless modules...
> > Is this about initramfs or why does it have to be DEFAULT_PACKAGES here?
> why do you think, that initramfs should be treated differently then any
> images? I for example find it weird, that one target has usable initramfs
> other doesn't. Those images can be used for many use cases, not only for
> installation of OpenWrt, but also for debugging and/or testing etc. Those
> images simply avoids trashing of the underlying storage medium.
Well, if you add stuff to DEFAULT_PACKAGES just because initramfs behaves
differently, who is treating it differently then?
The proper way IMO would be to either have initramfs use DEVICE_PACKAGES as
people would expect or create a separate parameter for _device_ initramfs
packages, which could default to DEVICE_PACKAGES then (so one could still
remove stuff if initramfs size is limited).
But I don't think moving everything to default packages is a good idea, as
it will only work for certain cases/packages, and dealing with "removed"
packages in DEVICE_PACKAGES is less convenient in make menuconfig.
> FYI I'm currently preparing daily runtime testing of snapshot/release-
> snapshot/latest-release on ipq40xx mvebu targets for the start (there is
> mvebu test on 19.07.6 for now as it doesn't boot). So as of today, ipq40xx
> passes the current very basic test suite and mvebu doesn't,
> 19.07.6 can't be even booted...
> 1. https://gitlab.com/ynezz/openwrt-device-runtime-testing/-
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
More information about the openwrt-devel