Hi,
I'm currently adding support for the AVM FRITZ!Box 3390 and 3490
devices. Both require a firwmare upload via MDIO to boot the separate
WiFi SoC.
In the corresponding PR at [1] we had a discussion on where to best
implement this MDIO downloader. As a consequence, I posted to
linux-netdev [2]
Hey,
I added TP-Link RE200v1 device support a few months ago. Currently, the
snapshot builds are broken - they started to break about 4 weeks ago.
The system does not even boot, the last output on serial is "Starting
kernel ..." from U-Boot. The initramfs image works fine.
The interesting thing
On 08/12/2020 00:53, Alberto Bursi wrote:
>
> On 08/12/20 00:12, Andreas Böhler wrote:
>> I added TP-Link RE200v1 device support a few months ago. Currently, the
>> snapshot builds are broken - they started to break about 4 weeks ago.
>> The system does not even boot, t
Hi,
I'm trying to add support for an older ZWave bridge, the MiCasaVerde
Vera Lite (similar or equal to SERCOMM NA300). It's based on RT3662,
64MB RAM and 32MB NAND flash - and this is where I'm currently stuck.
The rt3883.dtsi does not define a NAND controller and I'm unsure whether
there
Hi Daniel,
On 19/03/2021 01:52, Daniel Golle wrote:
Hi Andreas,
On Thu, Mar 18, 2021 at 10:42:35PM +0100, Andreas Böhler wrote:
How can I best find/add a NAND driver for RT3662, or is it not worth the
effort?
Good question, especially without the datasheet or any piece of code to
look
Hey Mika,
On 19/03/2021 11:12, Mika Laitio wrote:
I'm trying to add support for an older ZWave bridge, the MiCasaVerde
Vera Lite (similar or equal to SERCOMM NA300). It's based on RT3662,
64MB RAM and 32MB NAND flash - and this is where I'm currently stuck.
The rt3883.dtsi does not define a
On 02/02/2022 11:37, Torsten Duwe wrote:
Enable building Fritzbox x490 images, with UBI. The default is 252KiB LEB
size and 4k I/O, and the 7490 overriding it with half of those values.
Signed-off-by: Torsten Duwe
---
diff --git a/target/linux/lantiq/image/vr9.mk
Hey,
I've got a recent AVM FRITZ!Box 7530 with a KIOXIA TC58NVGS03H NAND IC.
Neither U-Boot nor Linux are able to read/write the NAND because the OOB
size is detected as 64 bytes instead of 128 bytes. I could get it to
work by:
1. Patching U-Boot qpic_nand.c with a fixup based on
Hey,
I'm trying to port OpenWrt to the Avaya WAP9102 / Xirrus XR620 AP.
According to internal pictures, it has a CN5020 CPU and 1GB of RAM. I
hooked up serial and started building images, TFTP boot is working fine.
I'm having a hard time getting the two GBit ports to work reliably. I
have a
Some newer OEM firmware files, even for existing devices, have the
fwup-ptn at offset 0x1050 instead of 0x1014. If the fwup-ptn header is not
found at 0x1014, the alternative offset at 0x1050 is tried.
Signed-off-by: Andreas Böhler
---
src/tplink-safeloader.c | 8 +++-
1 file changed, 7
Hi Sander,
thanks for the review.
On 28/01/2023 16:42, Sander Vanheule wrote:
Hi Andreas,
On Sun, 2023-01-22 at 22:36 +0100, Andreas Böhler wrote:
Some newer OEM firmware files, even for existing devices, have the
fwup-ptn at offset 0x1050 instead of 0x1014. If the fwup-ptn header
Hi,
back in January [1], I reported trouble with networking and PCIe on a
Avaya / Xirrus AP. In the meantime, I've found out that it uses a CN7020
CPU (not a CN5020 as previously believed) and that the PCIe driver does
not work properly (interrupts don't fire, setup is probably wrong).
Board file for ZTE MF287+ extracted from the device and repacked.
Signed-off-by: Andreas Böhler
---
board-zte_mf287plus.qca4019 | Bin 0 -> 24316 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 board-zte_mf287plus.qca4019
diff --git a/board-zte_mf287plus.qca401
ZTE MF287 extracted from the device and repacked.
Signed-off-by: Andreas Böhler
---
board-zte_mf287.qca4019 | Bin 0 -> 24308 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 board-zte_mf287.qca4019
diff --git a/board-zte_mf287.qca4019 b/board-zte_mf287.qca4019
new file mode
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi,
On 27/04/2024 00:40,
15 matches
Mail list logo