From: Richard Danter <richard.danter@windriver.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 750/107 CHRP question
Date: Thu, 31 Jul 2003 17:54:43 +0100 [thread overview]
Message-ID: <3F2949D3.8020106@windriver.com> (raw)
Hi All,
Sorry if this is a bit of a newbie question....
I am trying to port a 2.4.x kernel to a PPC750 board with a 107
controller. The board has a serial port connected to one of the ROM
select lines (at 0x7C000000) and I would like to use this as my console
port.
So far I can boot the board and see (via the serial port) the kernel
load addresses etc, and the kernel gets decompressed and starts to run.
This is all fine as the MMU is off at this point. However, when the
serial_console_setup() code starts trying to configure the serial port
again, I get a kernel panic as I am accessing an invalid mem space (MMU
now on!).
How do I map this correctly???
My build is based on the sandpoint but with all the init stuff for
devices, such as the RTC, removed. So I have the "standard" mapping in
the MMU_init code.
Many thanks
Rich
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-07-31 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 16:54 Richard Danter [this message]
2003-07-31 21:07 ` 750/107 CHRP question Matt Porter
2003-07-31 21:41 ` Richard Danter
2003-07-31 22:48 ` Matt Porter
2003-07-31 23:32 ` Wolfgang Denk
2003-08-01 8:16 ` Richard Danter
2003-08-01 4:34 ` Sangmoon Kim
[not found] <20030801082845.A38F6C602D@atlas.denx.de>
2003-08-01 9:02 ` Richard Danter
2003-08-01 12:17 ` Wolfgang Denk
2003-08-01 12:24 ` Richard Danter
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=3F2949D3.8020106@windriver.com \
--to=richard.danter@windriver.com \
--cc=linuxppc-embedded@lists.linuxppc.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).