Hi Jan, > > Introduce ERROR(), WARNING(), and INFO() console message output > macros > > to classify the messages and make their output more colorful so to > > increase readability for EBG's core output. > > > > Signed-off-by: Christian Storm <[email protected]> > > [...] > > +#define INFO(fmt, ...) > > \ > > + do { \ > > + PrintC(EFI_WHITE, L"> "); \ > > Only realized why trying out: What's the reason for the "> " prefix?
The reason is to differentiate EBG's core output from other output, e.g., by the watchdog driver probings. I thought about an "INFO" or no prefix but found this to be more outstanding while not overly intrusive nor too long. One can think about such a console printing infrastructure for the watchdog drivers as well (at the cost of introducing a dependency), then also including, e.g., DEBUG output to improve on, e.g., AMDFCH_WDT_DEBUG. That said, I don't have a strong opinion on the concrete measure though.. Kind regards, Christian -- Dr. Christian Storm Siemens AG, Technology, T RDA IOT SES-DE Otto-Hahn-Ring 6, 81739 München, Germany -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/9650a8522752444595272002524ba70d%40siemens.com.
