2010/3/19 W. Michael Petullo <m...@flyn.org>: >>> The WRT160NL gets shipped with a new bootloader since some time, which >>> actually checks the checksum in the trx image header. As the >>> checksummed area includes the jffs2 start marker, this will blow up >>> after first boot. >>> This patch fixes this by adding a new funktion to mtd (fixtrx) which >>> is called in firstboot. >> >> Nice patch. I was waiting for something like this since months. >> Some brcm63xx devices like Pirelli Alice Business Gate 2 Plus (1) >> and Alice Gate W2+ (2) has the same problem. >> Can this patch be extended to support this router's CFE bootloader? > > I'm a WRT160NL user, but I do not have this new hardware > revision. However, I am working on some documentation that I hope will > be applicable to the new hardware revision. > > Can anyone comment on when this should make it to subversion (I don't > see the patch in Trac yet)? > > Could someone provide the symptoms of using the new hardware without > this change? I understand this as the system will not boot the flash > image. Is this correct?
You can boot openwrt only once after flashing. On the second boot, the bootloader will throw a checksum mismatched error (if you have a serial cable attached to see it). > Could anyone provide any different markings that identify the new > hardware revision from older revisions? Not sure about serial numbers, the only but the bootloader version is different. > Are the changes made transparent to the older hardware revision? That is, > will a new build continue to work on the old hardware with no > configuration change? It shouldn't affect older hardware. > Thanks! > > -- > Mike > > :wq > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel