On 02/20/2014 12:28 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 19.02.2014 23:03, Paul Menzel wrote:
Am Mittwoch, den 19.02.2014, 00:47 +0100 schrieb Vladimir 'φ-coder/phcoder'
Serbinenko:
On 19.02.2014 00:18, Paul Menzel wrote:
But in general I think I agree with Vladimir. CBMEM console should be
supported and if not then that should be fixed.
I also agree, but it’ll take more time and the above is a good
work-around for the mean time.
Strongly disagree workarounds are like glue: they stick around. This one
is one that will stick around once implemented. It's better to avoid
workarounds if sane solution is within reach.
In this case you still haven't even named a single board where CBMEMC
doesn't work.
CBMEM console does not work for romstage on all AMD based boards. Ask
Rudolf and Kyösti for more details, but as far as I understood them, the
solution is *not* easy and not within reach at all.
As I already told the info from romstage is likely of minor importance
if the board boots. And if it doesn't, well no board status. If any of
the info from romstage is relevant it can be printed in ramstage as well
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.
Kyösti
--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
