public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@mimc.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 0.5sec delay when ttyO0 is enabled
Date: Tue, 18 Sep 2012 12:34:25 +0100	[thread overview]
Message-ID: <50585C41.1050704@mimc.co.uk> (raw)
In-Reply-To: <50584F90.2000606@mimc.co.uk>

On 18/09/12 11:40, Mark Jackson wrote:
> I'm using a BeagleBone, and the linux kernel from Koen Kooi (https://github.com/koenkooi/linux.git).
> 
> I have noticed there is a 0.5sec delay between OMAP UART0 being initialised and the console being
> enabled.

It is, of course, when the printk() messages are processed and dumped to the console.

If I boot with the "quiet" flag, the delay is magically gone.

Apologies for the noise.

  reply	other threads:[~2012-09-18 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 10:40 0.5sec delay when ttyO0 is enabled Mark Jackson
2012-09-18 11:34 ` Mark Jackson [this message]
2012-09-18 11:40 ` jean-philippe francois

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=50585C41.1050704@mimc.co.uk \
    --to=mpfj-list@mimc.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@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