Necromancing this thread... Sage has a patch to *optionally* use a serial console log in board_status.sh: http://review.coreboot.org/#/c/6094/
Earlier objections to such an approach seemed to stem from either: - Desire to use cbmem console instead. A fine idea, but on some platforms (especially those which use AGESA) a lot of information gets spit out to the console before cbmem is available. Re-factoring to make cbmem init happen earlier is unfeasible AFAICT. - Avoid confusing cbmem console log and other logs. This can be easily solved by using a different filename. I personally think it's best to only upload one log (whichever is most useful) and avoid polluting the web UI with redundant files. But I could live with multiple console logs if others feel strongly. Seeing as how only a small handful of people currently actually use this utility anyway, I'm inclined to think it's best to make the utility more useful for a major coreboot contributor get some more status reports uploaded. Thoughts? On Wed, Feb 19, 2014 at 3:14 PM, Kyösti Mälkki <kyosti.mal...@gmail.com> wrote: > On 02/20/2014 12:56 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > >> >> >>> You do not get raminit debug output printed in ramstage. >>> >>> Unfortunately, the case of incompatible DIMMs seems to be common one >>> with recent AGESA ports so information from romstage what DIMMs have >>> worked is actually relevant. >>> >> Just read this data from registers and print it. >> >>> >>> >> > Neither of us has probably looked closely what details we are missing from > AGESA romstages. I very much doubt it would be just static register > configuration on memory controllers that could be dumped afterwards. > > AMD has an amount of SMP init going on in romstage along with possibly > multiple logical CPUs using CAR etc. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot