From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Siva Prasad <sprasad@bivio.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: printk/console_init
Date: Tue, 13 Nov 2007 21:01:47 +1100 [thread overview]
Message-ID: <1194948107.18185.101.camel@pasglop> (raw)
In-Reply-To: <D83235F0F3C86D4D889D8B9A0DA8C6D7F73BF1@corpexc01.corp.networkrobots.com>
On Mon, 2007-11-12 at 18:54 -0800, Siva Prasad wrote:
> Hi,
>
> I am using 2.6.19 Linux on 8641D based system.
>
> I am using early printk's and it works fine until console_init() is
> executed. After that it does not, as the early printk's get disabled,
> which is fine. However, I don't see any prints after that at all, that
> are based on regular printk statements. I looked directly into the
> memory at __log_buf and found all the print messages. It is just not
> coming out to the serial port properly.
>
> It would be great if some one can tell me various parameters that I need
> to consider changing, to successfully port the serial driver for a new
> board.
>
> Based on the early printk's, I am getting the following messages...
You can use udbg-immortal to force the udbg early printk to stay around,
and then use printk to see what's going on with your serial driver.
Ben.
prev parent reply other threads:[~2007-11-13 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 2:54 printk/console_init Siva Prasad
2007-11-13 8:16 ` printk/console_init Geert Uytterhoeven
2007-11-14 2:28 ` printk/console_init - baud rate setting Siva Prasad
2007-11-14 11:30 ` Segher Boessenkool
[not found] ` <D83235F0F3C86D4D889D8B9A0DA8C6D7F73E14@corpexc01.corp.networkrobots.com>
[not found] ` <610b1b49ca582c7a2277e8d6dea2be31@kernel.crashing.org>
2007-11-15 2:17 ` Siva Prasad
2007-11-13 10:01 ` Benjamin Herrenschmidt [this message]
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=1194948107.18185.101.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sprasad@bivio.net \
/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;
as well as URLs for NNTP newsgroup(s).