No, LuCI uses util.ubus("system", "board"), which doesn't even expose
the internal board_name, but only the model name, so it will only see
the v10.
Automatic upgrade systems should also rely on the model name only, not
the board name.
The board name is really only an internal identifier. Reusing
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 her
On Mon, 26 Oct 2015 01:21:58 +0100
Matthias Schiffer 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
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 hav
Hi Matthias,
as long you can not flash the exact same image as v9,
you have to create a mips machine, but you can use the same setup
function as v9.
Many parts of openwrt use the mips machine to detect the board, like
sysupgrade.
Add your machine id to
target/linux/ar71xx/patches-4.1/700-MIPS-at
The TL-WR841N/ND v10 is mostly identical to the v9. Apart from some minor
changes, it contains a newer revision of the QCA9533 SoC and the CPU clock
is significantly higher.
Signed-off-by: Matthias Schiffer
---
target/linux/ar71xx/image/Makefile | 9 -
1 file changed, 8 insertions(+), 1
