Hi David,
On 30.01.2020 12:36, David Bauer wrote:
Hello again,
[...]
So I'm waiting on feedback from other owners of these boards and using this
(more or less) strange fix in the meantime.
Robert complained in the meantime, that my fix broke his R6260. He also sent me
the partition map of the stock firmware and it differs from mine (see below).
[...]
I'm still waiting for him to send ma a photo of the routers backside, but it
seems
we have to dynamically detect the partition map of the devices. I'll look into
the
SC_PART_MAP partition and the routers GPL code to find a possible solution for
this
problem.
There was some work with custom 'SC_PART_MAP' mtd parser back in 2018
but mapping used in vendor firmware didn't match what was in flash, see:
[0] and also [1] about 'different' R6220 models.
Added also Mathias and Chuanhong to the loop.
[0] https://github.com/openwrt/openwrt/pull/1318#issuecomment-419628452
[1] https://github.com/openwrt/openwrt/pull/1304
--
Cheers,
Piotr
In the meantime, I'll revert my "fix" to not break existing boards.
For the record: I assume this bug has nothing to do with the partition shifting
seen on the R6220, as the offending "feature" of the mtknand driver was disabled
in the meantime (and the partition map differs in the stock firmware). [0]
[0] https://github.com/openwrt/openwrt/pull/1304
Best wishes
David
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
