On 02/14/2013 07:30 AM, Nathan Hintz wrote: > On Wed, 2013-02-13 at 19:03 -0800, Nathan Hintz wrote: >> On Wed, 2013-02-13 at 22:46 +0100, Hauke Mehrtens wrote: >>> On 02/13/2013 10:33 PM, Chirag Chhatriwala wrote: >>>> Hi All, >>>> >>>> I've notcied a huge deal of progress with bgmac in the recent month and >>>> was willing to help bring support for the E4200v1. I own one of these >>>> devices but I'm not too familiar with the entire driver process. Also, I >>>> haven't flashed anything via serial/uart or JTAG as I'm simply familiar >>>> with flashing via tftp method. >>>> >>>> I've reached out to Rafal and Nathan for advice as well. >>>> >>>> Firstly, I wanted to know if there is anyone who owns one of these and >>>> can help with enabling OpenWrt support. I can certainly help in any way >>>> I can. I'm sure there are several folks out there who own one of these >>>> and I could mean a lot to revive their E4200v1 with OpenWrt support. >>>> >>>> I simply wish I had another one of these to donate to the OpenWrt devs >>>> for the cause. >>>> >>>> Thanks, >>>> Chirag >>>> >>> Hi Chirag, >>> >>> Your device should work, at least Ethernet wifi probably not. When you >>> have a serial console connected to your device just flash OpenWrt or >>> boot it from the network and report your results. >>> >>> Hauke >>> _______________________________________________ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel >>> >> Will the ethernet work if the device is not recognized >> by /etc/init.d/netconfig? It sounded like it had a different nvram >> value for "boardtype"? >> >> I've never booted my E3000 from the network, and tftp only works for me >> from a serial console using "upgrade code.bin" (I think my CFE is >> possibly broken). What command do you use when you boot from the >> network; and do you need a factory ".bin" image, or does the generic >> ".trx" work for this? >> >> Thanks, >> >> Nathan > > Hi Hauke: > > I saw that /etc/init.d/netconfig has additional "boardtype" values > added. Is the E4200v1 one of those added? Chirag didn't have an nvram > dump, but he had a reference to a tomato issue that indicated it might > be "0xF52C". Also, a patch had been added to the set maintained at > http://www.znau.edu.ua/temp/asus-rt-n16/2012-12-08T15-25/003-openwrt4716-TARGET_brcm4716-Linksys-E2000.patch > that indicated the E2000 has a "boardtype" of "0x04EF"; although the > same tomato reference has that one in lower case for WRT320N/E2000.
This list would have never been complete so now it is checked where the CPU port is and if it is port 8, this port is used instead of port 5 in the default switch configuration, see [0]. Hauke [0]: https://dev.openwrt.org/changeset/35597 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
