WarheadsSE wrote:And a way to do it per-device, as is correct. Since the install methods differ per-device.
kmihelich wrote:We will be relying on people not being retarded, which is a stretch, but it's the simplest solution. The 'linux' package will remain for compatibility purposes frozen at 3.1.10. It works, it's solid, no reason to do anything to it.
In the next couple days we'll be putting out a linux-kirkwood package with 3.4, containing a warning about u-boot compatibility. The package won't replace the linux package. This means it will be a conscious decision by the user to upgrade the kernel, which together with the warning implies they understand what's going on. If they don't, well, they were warned.
Wolfgang Denk wrote:When CONFIG_VERSION_VARIABLE is set in your board config file, then
U-Boot will set the "ver" envrionment variable to the current version
ID string. If you run "saveenv" at least once, then you can read this
string from the U-Boot environment under Linux, using the fw_getenv
tool / function provided in tools/env/ .
Users browsing this forum: No registered users and 1 guest