Re: [OpenWrt-Devel] [PATCH] ath79: archer-c7-v5: fix initramfs image

2020-06-19 Thread Baptiste Jonglez
On 19-06-20, Petr Štetiar wrote: > > On 17-06-20, Petr Štetiar wrote: > > > Currently it's not possible to tftpboot initramfs image as the image > > > contains tplink-v1-header which leads to: > > > > Out of curiosity, it looks like booting an initramfs image is only > > possible with serial

Re: [OpenWrt-Devel] [PATCH] ath79: archer-c7-v5: fix initramfs image

2020-06-19 Thread Petr Štetiar
Baptiste Jonglez [2020-06-19 10:22:57]: Hi, > On 17-06-20, Petr Štetiar wrote: > > Currently it's not possible to tftpboot initramfs image as the image > > contains tplink-v1-header which leads to: > > Out of curiosity, it looks like booting an initramfs image is only > possible with serial

Re: [OpenWrt-Devel] [PATCH] ath79: archer-c7-v5: fix initramfs image

2020-06-19 Thread Baptiste Jonglez
Hi, On 17-06-20, Petr Štetiar wrote: > Currently it's not possible to tftpboot initramfs image as the image > contains tplink-v1-header which leads to: Out of curiosity, it looks like booting an initramfs image is only possible with serial access to the bootloader? > ---

[OpenWrt-Devel] [PATCH] ath79: archer-c7-v5: fix initramfs image

2020-06-17 Thread Petr Štetiar
Currently it's not possible to tftpboot initramfs image as the image contains tplink-v1-header which leads to: ath> bootm ## Booting image at 8100 ... Bad Magic Number Fix this by using uImage wrapped initramfs image. Signed-off-by: Petr Štetiar ---