mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, keithp@keithp.com
Subject: Re: Is it possible to implement interrupt time printk's reliably?
Date: Mon, 10 May 2004 15:22:11 -0700 (PDT)	[thread overview]
Message-ID: <20040510222211.78262.qmail@web14922.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405102253330.8016-100000@phoenix.infradead.org>

So how long is the delay between PCI probe time (when the framebuffer goes
active) and when early user space is up with initrd? Or is initrd up first? If
initrd is up first then early user space mode setting will occur at the same
time that it does currently.

--- James Simmons <jsimmons@infradead.org> wrote:
> 
> > So how do printk's work in the very early boot? Is the video card active
> before
> > the kernel probes it's module, or are these very early printk's being queued
> > until the video driver is probed?
> 
> printk messages are stored in log_buf in printk.c. The console driver just 
> reads the buffer and displays what is in the buffer. Look at printk.c 
> carefully.
> 
>  
> 


=====
Jon Smirl
jonsmirl@yahoo.com


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

  reply	other threads:[~2004-05-10 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  2:52 Jon Smirl
2004-05-07  5:17 ` Andrew Morton
2004-05-07 13:34   ` Jon Smirl
2004-05-07 19:13     ` Andrew Morton
2004-05-07 19:26       ` Jon Smirl
2004-05-07 20:01         ` Andrew Morton
2004-05-09 16:33           ` Jon Smirl
2004-05-10 21:55             ` James Simmons
2004-05-10 22:22               ` Jon Smirl [this message]
2004-05-11  0:23                 ` James Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040510222211.78262.qmail@web14922.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=akpm@osdl.org \
    --cc=jsimmons@infradead.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®