Hi,
as decided in our combined vote, I've now finally closed all bugs reported for
lede-17.01 in bugs.openwrt.org (Flyspray).
This has been done based on a script, so I haven't looked at the individual
reports anymore.
Please note that there will be _no_ notification mails for these closures,
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
Thumb-2 code is denser than pure ARM, reducing RAM usage and improving
performance due to better instruction cache footprint.
There's no reason for not enabling this feature on other ARMv7 targets
(cortex-a7 and cortex-a8), but I don't have the hardware to test it.
Signed-off-by: Rui Salvaterra
m...@adrianschmutzler.de [2020-06-19 11:36:44]:
Hi,
> So, I wonder whether that's specific to the C7 v5 then or whether it would
> apply to the other tplink-safeloader-uimage devices as well?
nope, archer-c7-v5 is just a device I've found it on. It applies to all
safeloader devices which
Hi Petr,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Petr Štetiar
> Sent: Freitag, 19. Juni 2020 11:32
> To: openwrt-devel@lists.openwrt.org
> Cc: Petr Štetiar
> Subject: [OpenWrt-Devel] [PATCH] ath79: image: fix initramfs
Currently it's not possible to tftpboot initramfs image on archer-c7-v5
as the image contains tplink-v1-header which leads to:
ath> bootm
## Booting image at 8100 ...
Bad Magic Number
as U-Boot expect uImage wrapped image. This is caused by following
inheritance issue:
define
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
Good morning, Jason!
On Fri, 19 Jun 2020 at 00:50, Jason A. Donenfeld wrote:
>
> Hey Rui,
>
> I fixed it! It turned out to be caused by -fvisibility=hidden undoing
> the effect of the binutils fix from a while back. Here's the patch
> that makes the problem go away:
>
>
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?
> ---
