#20280: The Linksys EA6300v1/EA6400
------------------------------------+------------------------
Reporter: ewtoombs | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Keywords: ea6400,bcm4708,bcm53xx |
------------------------------------+------------------------
I've added preliminary support for the Linksys EA6300v1/EA6400. The power
LED and the WPS button aren't configured yet, but the RAM is correctly
configured and the 2.4GHz wireless works mostly.
There are problems. This router has partitions in its flash memory for a
main image and a backup image. This is the default partition table:
00000000: boot
00080000: nvram
00180000: devinfo
00200000: firmware
00200000: header
0020001c: kernel
00436430: / squashfs
01f00000: firmware2
01f00000: header
01f0001c: kernel
020d364c: / squashfs
03c00000: /var/config jffs2
08000000: END OF MEMORY
On the first flash, openwrt accidentally ignores its root filesystem and
instead mounts the root filesystem of the backup image on /, effectively
forcing the Linksys userspace to use the OpenWRT kernel. That only lasts
one boot though. OpenWRT erases everything after 0x01f00000 during the
first boot, replacing it with the UBIFS overlay so on the next boot,
openwrt's kernel does manage to find its root filesystem. Nothing happened
this time, but running the Linksys userspace with the openwrt kernel is
dangerous and shouldn't even happen once.
Also, I'm pretty sure the wireless b/g/n interface doesn't work in Managed
mode. Master mode works fine, though. Any reason why that might be? Is it
hardware or software? The hardware was only meant to work in Master mode,
after all.
The files I used to build my image are attached.
--
Ticket URL: <https://dev.openwrt.org/ticket/20280>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
