From: "mike zheng" <mail4mz@gmail.com>
To: linuxppc-dev@ozlabs.org.
Subject: Early UART setup on 2.6 kernel for mpc85xx
Date: Fri, 10 Aug 2007 21:43:41 -0400 [thread overview]
Message-ID: <5c9cd53b0708101843q1b39bccfv10e98eccaa834c91@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Hi All,
In order to debug the kernel 2.6, I want setup serial port with UART on
mpc85xx as early as possible. I add the register access code at the
beginning of platform_init(). For example, I try to write THR
register(0xe0004500). However the system just hanging there with this line.
If I comment out this line, everything works fine.
Here is the code my mpc85xx_cds_common.c:
void __init
platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
unsigned long r6, unsigned long r7)
{
....
}
[-- Attachment #2: Type: text/html, Size: 858 bytes --]
next reply other threads:[~2007-08-11 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 1:43 mike zheng [this message]
[not found] <mailman.1.1186797602.26064.linuxppc-dev@ozlabs.org>
2007-08-13 11:09 ` Early UART setup on 2.6 kernel for mpc85xx Morrison, Tom
2007-08-13 15:53 ` Scott Wood
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=5c9cd53b0708101843q1b39bccfv10e98eccaa834c91@mail.gmail.com \
--to=mail4mz@gmail.com \
--cc=linuxppc-dev@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).