On 09.11.2010, at 19:11, Peter Stuge <[email protected]> wrote: > Stefan Reinauer wrote: >>> This would be the easy place to make sure that you could see the messages. >>> #define MALLOCDBG(x...) printk(CONFIG_DEFAULT_CONSOLE_LOGLEVEL, x) >> >> I think keeping them at SPEW is fine,... Otherwise we end up with >> images printing that information at ie error log level making it >> impossible to enable the option in production images at all. > > Hm? Please clarify? > > The image would print the information only when the user selects RAM > debug, but it would work better than now, because that option could > always be selected, regardless of what maximum (or default) loglevel > was selected.
What if one wants to build an image with ram debug capability that only prints errors unless spew is enabled via CMOS? > > Currently the option is only shown if loglevel >= DEBUG > > > //Peter > > -- > coreboot mailing list: [email protected] > http://www.coreboot.org/mailman/listinfo/coreboot >
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
