Ticket #316 (Fixed)Wed Sep 19 11:58:15 UTC 2012
Common ResetCMOS file in boot hook is risky
Reported by: | Sprow (202) | Severity: | Normal |
Part: | RISC OS: Application | Release: | |
Milestone: | Status | Fixed |
Details by Sprow (202):
This is referring to the file named “ResetCMOS” which is used by some of the configure plugins to know what the factory default was when selecting the “Default” button.
Previously there was a 1:1 mapping between OS version and machine, so it was safe to have a ResetCMOS file per hook directory.
This is no longer true (eg. default for IOMD would be to have 1 ADFS harddisc, but ADFS doesn’t feature in OMAP3 for example), so there needs to be some way for the plugins to figure out what the default should be.
Random ideas
a) add a NVMemory reason code to the kernel to allow its ROM default table to be retrieved
b) put multiple ResetCMOS files into some kind of machine hierarchy in boot hook
Changelog:
Modified by Sprow (202) Thu, January 10 2013 - 21:24:31 GMT
- Status changed from Open to Fixed
OS_NVMemory subreason added in Kernel-5_35-4_79_2_180
Configure library makes use of it in Configure-0_10