From: Dan Malek <dan@embeddedalley.com>
To: Kalle Pokki <kalle.pokki@iki.fi>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CPM2 early console
Date: Sun, 2 Oct 2005 12:59:11 -0400 [thread overview]
Message-ID: <26a6f673ac9438729eccfe0c376c6b3d@embeddedalley.com> (raw)
In-Reply-To: <433E2530.7090503@iki.fi>
On Oct 1, 2005, at 1:57 AM, Kalle Pokki wrote:
> Yes I'm sure the code in Linux is right. It may be missing some
> initialisation it depends on, but anyway.
Did you mention in the past you have a custom boot loader? Is this
something
other than the PlanetCore boot rom?
> My board is an Embedded Planet EP8248 that came with a pre-installed
> version of Linux 2.4. That version works ok, though I don't know what
> modifications were made to the kernel. The source wasn't included...
I doubt they made any modifications to the generic driver. The only
thing
they may have done is added some board control register/GPIO to enable
the RS-232 transceiver. If you don't have their board initialization
functions,
though, this would be useful.
> Currently I boot with PlanetCore, load my own boot loader (I'm going
> to use it exclusively when my own custom board based on 8247 comes
> out) via tftp, and start the most recent kernel.org kenel from it.
What about just trying to boot the new kernel from PlanetCore boot rom?
Of course, if you are doing your own boot rom and have a board to bring
up,
you should have invested in something like a BDI2000 long ago because
it will
have paid for itself many times over by the time you are done :-) It
would have
also allowed you to debug this problem rather quickly.
You are going to have to investigate your processor state prior to
calling
Linux (HIDx registers, cache and MMU state, SIU configuration, etc) to
see
how it differs from what PlanetCore does. There are lots and lots of
options
on these processors, and one bit in one configuration register that is
incorrect can cause lots of grief.
-- Dan
next prev parent reply other threads:[~2005-10-02 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:02 CPM2 early console Rune Torgersen
2005-09-22 16:05 ` Kumar Gala
2005-09-23 10:55 ` Kalle Pokki
2005-09-27 14:11 ` Kalle Pokki
2005-09-27 16:39 ` Dan Malek
2005-09-27 20:35 ` Kalle Pokki
2005-09-27 20:48 ` Dan Malek
2005-09-28 10:20 ` Kalle Pokki
2005-09-29 12:24 ` Kalle Pokki
2005-09-29 12:50 ` Dan Malek
2005-09-30 13:22 ` Alex Zeffertt
2005-09-30 13:42 ` Alex Zeffertt
2005-09-30 20:16 ` Kalle Pokki
2005-09-30 13:58 ` Dan Malek
2005-09-30 20:10 ` Kalle Pokki
2005-09-30 20:28 ` Dan Malek
2005-10-01 5:57 ` Kalle Pokki
2005-10-01 8:24 ` Roger Larsson
2005-10-02 16:59 ` Dan Malek [this message]
2005-10-03 7:04 ` Kalle Pokki
2005-10-04 8:13 ` Kalle Pokki
2005-10-04 9:59 ` Alex Zeffertt
2005-10-04 10:16 ` Kalle Pokki
2005-10-04 16:04 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 13:11 Kalle Pokki
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=26a6f673ac9438729eccfe0c376c6b3d@embeddedalley.com \
--to=dan@embeddedalley.com \
--cc=kalle.pokki@iki.fi \
--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).