On Sun, Feb 9, 2014 at 4:50 AM, Paul Menzel < paulepan...@users.sourceforge.net> wrote:
> Dear coreboot folks, > > > currently no coreboot messages are stored for boards not supporting > CBMEM console (or where this option is disabled (currently by default)) > or no coreboot *romstage* messages are stored for boards, where the data > cannot be preserved (passed to 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. > I don't think the script itself should be responsible for collecting serial output. Instead, how about adding an argument to override the default behavior of running "cbmem -c" on the target so that the user can pass in a filename? The user will simply capture the serial output using whatever tool they like, dump the output to a text file, and run the script with an argument to use the file instead of calling "cbmem -c". Here is a proof-of-concept: http://review.coreboot.org/#/c/5191 . But in general I think I agree with Vladimir. CBMEM console should be supported and if not then that should be fixed. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot