Re: [OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-30 Thread David Bauer
Hello Piotr, On 1/30/20 12:57 PM, Piotr Dymacz wrote: >> 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

Re: [OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-30 Thread Piotr Dymacz
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

Re: [OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-30 Thread David Bauer
Hello again, On 1/30/20 1:11 AM, David Bauer wrote: > Yes, I've checked the partitioning (and it is off). However, I still opted to > push the > other fix, as I'm unsure whether or not the partition mapping is off for all > boards or only > my specific R6260, as the partition map seems to

Re: [OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-29 Thread David Bauer
om; achte...@googlemail.com; openwrt-devel > de...@lists.openwrt.org> >> Subject: [OpenWrt-Devel] Netgear R6260 EEPROM location >> >> Hi, >> >> while testing my shiny new NETGEAR R6260 with OpenWrt, i was experiencing >> very bad >> receptio

Re: [OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-29 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On > Behalf Of David Bauer > Sent: Dienstag, 28. Januar 2020 21:05 > To: drvl...@gmail.com; achte...@googlemail.com; openwrt-devel de...@lists.openwrt.org> > Subject: [O

[OpenWrt-Devel] Netgear R6260 EEPROM location

2020-01-28 Thread David Bauer
Hi, while testing my shiny new NETGEAR R6260 with OpenWrt, i was experiencing very bad reception as well as throughput. Upon closer inspection, it turns out that the EEPROM is read from an incorrect offset. The Offset positions here are: - 0x28000 for 5GHz - 0x2 for 2.4GHz Can someone