All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: "Ardelean, Andrei" <Andrei.Ardelean@idt.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
	Ricardo Mendoza <ricmm@gentoo.org>,
	linux-mips@linux-mips.org
Subject: Re: The new "real" console doesn't display printk() messages like "early" console!
Date: Mon, 22 Nov 2010 13:02:56 -0800	[thread overview]
Message-ID: <4CEADA80.8030605@caviumnetworks.com> (raw)
In-Reply-To: <AEA634773855ED4CAD999FBB1A66D0760136A91F@CORPEXCH1.na.ads.idt.com>

On 11/22/2010 12:51 PM, Ardelean, Andrei wrote:
> Hi Sergei,
>
> "     Are your UART registers identity mapped to virtual address space?"
>
> My system has DDR memory 0x80000000..0x90000000 (kseg0) and UART is
> mapped starting with bbf01000 (kseg1). Can you give me some details
> about your question?
>
> I didn't do anything special for the port other than
> 	set_io_port_base(GD_PORT_BASE);
> in gd-init.c
>
>

I think you need to reset your process here.

First you should probably get a prom_putchar() function working.  Then 
enable CONFIG_EARLY_PRINTK.  That will enable you to debug many things.

If need be, you can write a trivial prom_puts() to go with your 
prom_putchar().

If you have two serial ports available, all the better.  Use one for 
printing debugging information and the other as the port you are trying 
to debug.

Asking people to stare at the thousands of lines of code that make up 
the serial I/O system and spot the error in your configuration will 
probably be less fruitful than tracing through it to find the problem.

David Daney

      reply	other threads:[~2010-11-22 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 18:55 The new "real" console doesn't display printk() messages like "early" console! Ardelean, Andrei
2010-11-18 18:55 ` Ardelean, Andrei
2010-11-18 19:20 ` Sergei Shtylyov
2010-11-18 20:04   ` Ardelean, Andrei
2010-11-18 20:04     ` Ardelean, Andrei
2010-11-18 21:21     ` Ricardo Mendoza
2010-11-18 22:01       ` Ardelean, Andrei
2010-11-18 22:01         ` Ardelean, Andrei
2010-11-18 23:58         ` Ricardo Mendoza
2010-11-19 14:04           ` Ardelean, Andrei
2010-11-19 14:04             ` Ardelean, Andrei
2010-11-19 16:08         ` Sergei Shtylyov
2010-11-22 16:37           ` Ardelean, Andrei
2010-11-22 16:37             ` Ardelean, Andrei
2010-11-22 20:51           ` Ardelean, Andrei
2010-11-22 20:51             ` Ardelean, Andrei
2010-11-22 21:02             ` David Daney [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=4CEADA80.8030605@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=Andrei.Ardelean@idt.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ricmm@gentoo.org \
    --cc=sshtylyov@mvista.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.