OK - so after a bit more digging into things (and a poke by Mike) - I think
most of the stuff already exists.
Normal run time issues:
--------------------------
- MTD_OOPS - on 2007-06-28 this was added to Linus's tree:
http://lkml.org/lkml/2007/6/18/234
CONFIG_MTD_OOPS
tristate "Log panic/oops to an MTD buffer"
depends on MTD
help
This enables panic and oops messages to be logged to a circular
buffer in a flash partition where it can be read back at some
later point.
To use, add console=ttyMTDx to the kernel command line,
where x is the MTD device number to use.
Note - this currently _only_ does things when oops_in_progress is set, but
should be easy to extend to all - if that what people want.
- mtd devices can be backed by RAM.
CONFIG_MTD_RAM
- mtd devices can be backed by flash (if you want things to be persistant
across power cycles)...
early boot issues:
----------------------
- CONFIG_EARLY_PRINTK
- early printk just defined a console - and is supported by:
alpha, blackfin, microblaze, mips, powerpc, sh, x86
- it's pretty trivial to support a memory based buffer - some
archs already support it.
I think this only leaves Wolfgang's desire for memory buffers from the
bootloader to get (somehow) into the kernel's log buffer for syslog
processing...
Anyone else agree?
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
