[OpenWrt-Devel] [RFC PATCH] ath79: clarify purpose of factory image

[Henrique de Moraes Holschuh]

On 26/03/2020 12:56, Adrian Schmutzler wrote:
> While the purpose of a factory image in general is to flash a
> device with vendor OS "directly", some vagueness has evolved over
> the years with respect to additional uses of these images.
> 
> One common case is when a device supports TFTP recovery.
> Particularly with TP-Link devices in ar71xx/ath79, it is common
> that the factory image can be flashed via TFTP without any additional
> measures. In contrast, on some ramips devices the same procedure might
> overwrite your u-boot partition and make the device unbootable.
> However, in both cases you might only have a factory.bin which
> won't reveal any further information just by itself.
> 
> To improve the situation at least a bit, this commit tries to
> clarify the image names by introducing the following three schemes:
> 
> factory.bin - used from vendor OS, _not_ suitable for TFTP
> factory-tftp.bin - used from vendor OS, _also_ suitable for TFTP
> tftp.bin - can _not_ be used from vendor OS, but can be used via TFTP

The name "tftp-recovery" (maybe "tftp_recovery") has already seen some 
use on images built for the purposes of being used for TFTP, maybe it 
would be better to keep that naming?

-- 
Henrique de Moraes Holschuh
Analista de Projetos
Centro de Estudos e Pesquisas em Tecnologias de Redes e Operações 
(Ceptro.br)
+55 11 5509-3537 R.:4023
INOC 22548*625
www.nic.br

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel