[OpenWrt-Devel] [PATCH 1/2] include/image.mk: Introduce option to wrap kernel into JFFS2

Benjamin Berg benjamin at sipsolutions.net
Mon Nov 2 18:53:53 EST 2015

On Mo, 2015-11-02 at 20:49 +0100, Felix Fietkau wrote:
> On 2015-11-02 20:33, Benjamin Berg wrote:
> > Some devices like the NBG6616 and NBG6617 expect the kernel to be
> > in a JFFS2 partition. This macro allows wrapping the kernel so that
> > a normal squashfs+jffs partition can be used for the rest of the
> > firmware.
> Does that board run u-boot? If it does, you may want to use the padjffs2
> utility to force it to stop scanning after the end of the filesystem image.
> In case the boot loader scans the whole filesystem, this will also
> prevent it from parsing data from OpenWrt's jffs2 overlay.

Sounds good. I was simply looking at the ZyXELNAND target, which does
not do that currently. Only realized now that mkubntkernelimage is
pretty much identical and does the padding already.

So, the new plan would be to merge mkubntkernelimage with what I stared
with the jffs2 definition. That way both models can use the same
definition and the ubnt-uap-pro KERNEL line changes from
  KERNEL := kernel-bin | patch-cmdline | lzma | uImage lzma | mkubntkernelimage
  KERNEL := kernel-bin | patch-cmdline | lzma | uImage lzma | jffs2 kernel0

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20151103/88641241/attachment.sig>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list