Skip to contentSkip to conversation

x86_64: don't use early_printk() during memory init

PATCH Chuck Ebbert 1 participant 1 message Feb 25, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 8 lines · Andi Kleen
Quoted 4 lines

printk is working by the time this memory init message prints. As it stands, output jumps to the top of the screen and prints this message, then back to normal boot messages, overwriting a line at the top.

Using of early_printk here was intentional because it needs much less infrastructure than printk and is pretty good proof that the kernel at least started.

Well it made me think something had gone horribly wrong and was
scribbling over video memory. Especially since it left debris at the end of the line... and you don't want to fix that either.

Signature · 2 lines
Chuck
"Equations are the Devil's sentences."  --Stephen Colbert