mips: no need in architecture specific implementation of do_printk
With the proper configuration flags enabled, do_printk is available from src/console, no need to define it elsewhere. BUG=chrome-os-partner:31438 TEST=with upcoming patches, the urara board coreboot builds fine Change-Id: Ib1e3e5750cdc1adc509b4580a4f24d3ff3b105ee Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/215862 Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
e32d7a7e54
commit
69c655537c
1 changed files with 0 additions and 17 deletions
|
|
@ -36,20 +36,3 @@ void console_tx_flush(void)
|
|||
uart_tx_flush();
|
||||
#endif
|
||||
}
|
||||
|
||||
int do_printk(int msg_level, const char *fmt, ...)
|
||||
{
|
||||
va_list args;
|
||||
int i;
|
||||
|
||||
if (msg_level > console_loglevel)
|
||||
return 0;
|
||||
|
||||
va_start(args, fmt);
|
||||
i = vtxprintf(console_tx_byte, fmt, args);
|
||||
va_end(args);
|
||||
|
||||
console_tx_flush();
|
||||
|
||||
return i;
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue