On 09.02.2014 13:50, Paul Menzel wrote: > Dear coreboot folks, > > > currently no coreboot messages are stored for boards not supporting > CBMEM console Is there any remaining? If so it's an issue to be fixed > (or where this option is disabled (currently by default)) Change the defaults. > or no coreboot *romstage* messages are stored for boards, where the data > cannot be preserved (passed to ramstage). > which boards are concerned? Which boards use ROMCC for romstage? Do they output anything useful in romstage? If so, can't it be compensated by ramstage? > Using the serial (or USB) console all these messages can be captured > with no problem, so I propose to just add these captured messages into > the file `serial_console.txt`. Of course this file probably contains > also the payload and (Linux) kernel log, but I think that is fine. > > SeaBIOS’ `readserial.py` should be used for capturing the messages as it > adds time stamps. > > Scripting this is going to be hard, as the log is captured on a > different system. So for now I propose to add it manually. > Having to capture serial makes setup needed for board-status more difficult. Certainely, one needs to have a recovery method for case of brick but having a complete serial setup will heavily reduce board-status input which already isn't huge. > > Thanks, > > Paul > > >
signature.asc
Description: OpenPGP digital signature
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot