[PATCH v2] mt7621: move uboot-envtools to DEFAULT_PACKAGES
Peter Naulls
peter at chocky.org
Tue Feb 28 04:45:04 PST 2023
On 2/28/23 06:46, Bjørn Mork wrote:
> Peter Naulls <peter at chocky.org> writes:
>> On 2/27/23 17:23, Hauke Mehrtens wrote:
>>
>>> This will add uboot-envtools to all devices. uboot-envtools is not
>>> included in all DEVICE_PACKAGES now, should we explicitly remove it
>>> from device definitions which do not had it before?
>>> The Device/adslr_g7 for example does not add uboot-envtools in its
>>> DEVICE_PACKAGES.
>>>
>>
>> Same comment for NAND support. Only 1/3rd or so of the mt7621 systems
>> use the nand feature.
>
> This is a difficult problem for any feature which is required by one or
> more device during boot or upgrade. Using a shared rootfs per target
> means that all such features must be included on all devices.
>
> The alternatives are AFAICS
> 1) splitting targets by feature sets
> 2) always use a per-device rootfs
>
> I believe 2) is non-trivial. 1) might be easier and could make some sense
> for huge targets like mt7621?
Well, I certainly agree. I have this situation. I have a separate build
system, which setups an overlay per device (3x mt7621 boards) in files and then
also does some post-processing to the rootfs via a change I put in the end
of the OpenWrt scripts. But one solution here might be per-target
package selection - I can imagine this getting messy though.
More information about the openwrt-devel
mailing list