stevenh512 wrote: hhm1 wrote:
The wireless and wired is working now. They are not currently on by default, though. Currently, a firmware image needs to be built, using the source code, with the following modifications...
I'm coming here from DD-WRT and wanting something more customizable, so it's nice to see this is working. Am I correct in assuming that if the E1000 works, the WRT160Nv3 (same hardware) should also work? If so I'm willing to help test this, I'm new to OpenWRT but I have some C, C++ and Ruby programming experience and I already have the Buildroot installed on my machine (Ubuntu 12.10 64-bit).
My guess is yes, but I really do not know for certain. Seeing how different their firmware images are might tell more; the sources are available here; the E1000 source is not currently up, there is a link to a request form there though, and they responded for me pretty fast (for sources for E1000 and M10).
I would say that if you think you can access the serial console if needed, just in case of bricking, you probably can upload it without worries.
(That is how I started soldering; I first learnt soldering on my E1000, when taping the wires was not working. Then the Arduino Uno becomes my usb-to-serial adapter; wrote a tutorial here)
I think it will work; the main thing as far as I know, that could stop it, would be the bootloader (comparing 160N bootlogs and e1000 bootlogs might give useful info); I think the bootloaders are at least somewhat similar. Uploading the image from DD-WRT might be better than uploading it from stock firmware, though. (I sometimes uploaded it from dd-wrt and sometimes via serial/TFTP)
Other than enabling kmod-bgmac and applying the patch, is there anything special I need to do to the config (assuming I'm starting with the config.brcm47xx_generic from the most recent Attitude Adjustment build)?
I use the svn trunk, attitude adjustment might be too old; the bgmac driver was released after AArc1. As far as the config: as far as I know, that should be all that is needed.