Am Dienstag, 7. April 2020, 16:22:37 CEST schrieb Hannu Nyman:
> I do not think that there is a nice clean solution, as I do not remember
> seeing a solution of different packages for iniramfs, factory and sysupgrade
> images.
>
> I would approach that with a two-step build process, using two
Hi Bjoern,
I made a patch for include/image-commands.mk that allows to building squashfs
initrd images.
The reason for me is that the imagebuilder is unable to generate initramfs
images.
When building the final images with the imagebuilder you can define which
packages to include.
Your
Tomasz Maciej Nowak writes:
> In include/kernel-defaults.mk there is
> INITRAMFS_EXTRA_FILES ?=
> $(GENERIC_PLATFORM_DIR)/image/initramfs-base-files.txt.
> Maybe You could add a logic for ignore files list if they exist. No other
> solution comes to my mind.
Thanks for the suggestion. But I
Hi Bjørn.
W dniu 07.04.2020 o 16:50, Bjørn Mork pisze:
> Hannu Nyman writes:
>
>> I do not think that there is a nice clean solution, as I do not
>> remember seeing a solution of different packages for iniramfs, factory
>> and sysupgrade images.
>>
>> I would approach that with a two-step build
Hannu Nyman writes:
> I do not think that there is a nice clean solution, as I do not
> remember seeing a solution of different packages for iniramfs, factory
> and sysupgrade images.
>
> I would approach that with a two-step build process, using two .config
> recipes:
>
> * First a build with
I do not think that there is a nice clean solution, as I do not remember
seeing a solution of different packages for iniramfs, factory and sysupgrade
images.
I would approach that with a two-step build process, using two .config recipes:
* First a build with a smaller .config recipe without
The device I am playing with (ZyXEL WAP6805) can be upgraded to OpenWrt
by tftp'ing an OpenWrt initramfs image to it. But the image *must* be
less than 6815744 bytes, which is a hard coded limit in the OEM tftp
server.
The device also includes a Quantenna module, which needs a rather large
