> Errata corrige: maybe I used the wrong term, I meant "volatile" instead > of "temporary" information, i.e. I'd like to save this info to re-read > it later but I don't want to store it in flash, a simple log, run-time > information for debug like a flight-recorder or whatever you want. I'm puzzled by the use of "a generic piece of memory" to store "persistent" things (Perhaps this is made clear in the 17 parts of the patch? I haven't read them yet). On x86 f/w typically clears all of memory on reset ... so you only get persistence if you use kexec to get from the old kernel to the new one. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
