Re: [patch] x86_64: don't use early_printk() during memory init

On Saturday 25 February 2006 02:45, Chuck Ebbert wrote:
> 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.

So please don't apply the patch.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [patch] x86_64: don't use early_printk() during memory init
  - From: Chuck Ebbert <[email protected]>

Prev by Date: Re: [patch] x86: clean up early_printk output
Next by Date: Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
Previous by thread: [patch] x86_64: don't use early_printk() during memory init
Next by thread: RE: raid over sata - write barrier
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]