ARM: Separate the early console (romstage) from the bootblock console.
It might be that you want an early console in romstage before RAM is up, but you can't or don't want to support the console all the way back in the bootblock. By making the console in those two different environments configurable seperately that becomes possible. On the 5250 console output as early as the bootblock works, but on the 5420 it only starts working in the ROM stage after clocks have been initialized. BUG=chrome-os-partner:19420 TEST=Built and booted on pit with another change and an external tool, and was able to get serial output. Built for snow. BRANCH=None Change-Id: Ie27ae7a7b22f336d23893618969efde4145fefd7 Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://gerrit.chromium.org/gerrit/57725 Reviewed-by: Stefan Reinauer <reinauer@google.com> Commit-Queue: Gabe Black <gabeblack@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org>
This commit is contained in:
parent
bcb646d693
commit
53119fdeab
10 changed files with 31 additions and 18 deletions
|
|
@ -84,7 +84,8 @@ void mainboard_post(u8 value);
|
|||
void __attribute__ ((noreturn)) die(const char *msg);
|
||||
int do_printk(int msg_level, const char *fmt, ...) __attribute__((format(printf, 2, 3)));
|
||||
|
||||
#if defined(__PRE_RAM__) && !CONFIG_EARLY_CONSOLE
|
||||
#if defined(__BOOT_BLOCK__) && !CONFIG_BOOTBLOCK_CONSOLE || \
|
||||
(defined(__PRE_RAM__) && !defined(__BOOT_BLOCK__)) && !CONFIG_EARLY_CONSOLE
|
||||
|
||||
static inline void printk(int LEVEL, const char *fmt, ...);
|
||||
static inline void printk(int LEVEL, const char *fmt, ...) {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue