From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Help ! 2.6.14 kernel can't bring up
Date: Fri, 18 Nov 2005 18:14:53 -0500 [thread overview]
Message-ID: <437E606D.20601@dlasys.net> (raw)
In-Reply-To: <20051118024803.E2988687A1@ozlabs.org>
zjznliang wrote:
> Hi linuxppc-embedded!
>
> Hi , How to config the "early printk" in 2.6.14 linux configration???
>
>
>
Console and debugging I/O is available at all stages of The Linux
loading process - If the drivers for your board support it.
There is nearly free support for 8250 like serial ports, in virtually
all boards. Support for other debugging IO devices is fairly simple to
setup.
I used the arch/ppc/syslib/mv64x60_dbg.c and
arch/ppc/boot/simple/mv64x60_tty.c as templates to create trivial
drivers for debugging IO
on hardware that had no relation to a UART.
I think "early printk" refers to the early serial driver that can be
used after the kernel has uncompressed itself and relocated itself and
switched to
a virtual environment. For 8250 like serial ports that can enabled in
the linux .config file setup by make menuconfig or whatever variant of
make xxconfig
you prefer. For non-8250 like uarts you will again have to write an
early serial driver. All the early debug IO drivers are trivial - little
more is needed than
an implementation of putc, as opposed to the full conolse support
required for a tty on a booted system.
next prev parent reply other threads:[~2005-11-18 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 2:02 Help ! 2.6.14 kernel can't bring up zjznliang
2005-11-18 18:44 ` Clemens Koller
2005-11-18 23:14 ` David H. Lynch Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 15:54 David H. Lynch Jr
2005-11-17 7:50 zjznliang
2005-11-17 11:02 ` Clemens Koller
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=437E606D.20601@dlasys.net \
--to=dhlii@dlasys.net \
--cc=dhlii@comcast.net \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).