After taking some time to think about this. Wouldn't luci tell the user it's running on a 841 v9? This could confuse them because a v9 sysupgrade wouldn't work. sysupgrade fails then. Also an automatic upgrade based on system info wouldn't work either.
As long we don't have dts support, I see here two solution. Add another mips machine or change the board detection to detect this difference. Best, lynxis On Mon, 26 Oct 2015 15:28:09 +0100 Alexander Couzens <lyn...@fe80.eu> wrote: > On Mon, 26 Oct 2015 01:21:58 +0100 > Matthias Schiffer <mschif...@universe-factory.net> wrote: > > > Thanks, but I know what I'm doing. The hardware is similar enough to > > boot with the exact same initialization routines as the v9, thus > > reusing the BOARDNAME is fine (it is done like this for other > > hardware as well - OpenWrt has a distinction between "board" and > > "model", where multiple models can have the same board, but still > > each model has its own images) > > > > On TP-LINK devices, sysupgrade checks the TPLINK_HWID of the image > > against the one in the flash, the BOARDNAME doesn't matter (except > > to determine that it is a TP-LINK device). > > Sorry, no offensive. I forgot the tplink specific check within > sysupgrade. -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604
pgpnPCcVPhvn6.pgp
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
