... which is why I would have been happy to ignore their 'restriction' in relation to Uboot as it simply cannot apply to the Uboot part of their SDK.
I understand that the link to the SDK I gave is based on UBoot 1.1.3, but I would have thought that Ralink themselves would have done something to fix the issue from their Ralink 3.3 version of Uboot to their version 4.0. OK, I take your counsel that this is not the case, but despite searching far and wide I am still not closer to an answer to my question as to what to do and what to compile. The email you posted earlier in reply to my original email, thank you very much for that, references the Ralink 3.3 ASoC SDK (Ralink_ApSoC_SDK_3301.tar.bz2) which itself is based on the UBoot 1.1.3. so if you say do not use the Wive Uboot version because it is based on UBoot 1.1.3' what is the relevance if the Ralink Uboot version 3.3, which is based on Uboot 1.1.3 just the same? So what uboot bootloader version am I supposed to use for rt350x? Is the standard Uboot Version for MIPS going to work? And which one? John seemed to be aware of the bug but which UBoot version is the bug actually fixed in? As you can probably tell I am not used to deal with bootloaders. Maybe I am overcomplicating things or do not see the wood for the trees but I am left none the wiser as to what to do to upgrade the bootloader on this rt305x device so that there is no leakage of network traffic during boot. > On 14/01/2014, at 7:38 pm, Michel Stempin <michel.stem...@wanadoo.fr> wrote: > > There is no hard work there at all. > > From commit messages: "Uboot: up from 3.4.0.0 sdk and fix mtd map." > > So this is just a fresher Ralink SDK 3.4.0 modified U-Boot, still based on > the old U-Boot 1.1.3 version. > > And the Wive license is a pure abuse, since U-Boot is covered by the GPL, > which prevents from adding any restriction on the source distribution: > > "WIVE FIRMWARE FREE ONLY FOR NOT COMMERCIAL (INDIVIDUAL) USE. Conditions of > commercial use (include preinstall, rebranding and others) are discussed > individually by e-mail." > > -- > Michel > > Le 14/01/2014 00:06, Hanno Schupp a écrit : >> Somebody seems to have done all the hard work already merging Ralink I boot >> modifications back into uboot bootloader code for the rt2880/rt305x >> platform: >> https://gitorious.org/wive-rtnl-ralink-rt305x-routers-firmware/wive-rtnl-ralink-rt305x-routers-firmware/source/e568932211ea59ff3b09bf2839859de3eb5502f7:Uboot >> >> Does that look like the right approach and might that bootloader work? Your >> thoughts? >> >> >> >>> On 13/01/2014, at 11:52 pm, Michel Stempin <michel.stem...@wanadoo.fr> >>> wrote: >>> >>> Ralink_ApSoC_SDK_3301.tar.bz2 >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
