public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Daniel Wu <Daniel.Wu@alcatel•com.au>
To: linuxppc-embedded@lists•linuxppc.org
Subject: Re: Porting LinuxPPC
Date: Tue, 23 May 2000 17:18:36 +1000	[thread overview]
Message-ID: <00May23.171838est.115222@border.alcanet.com.au> (raw)
In-Reply-To: 392562CE.A71A4F49@embeddededge.com


Hi,

Thanks to all who responsed to my last qeustion. The problem was that the immr
was not setup correctly. Also since it is a custom board (MPC860T based), I had
to rewrite code to fill in the bd_t structure. The board is now sending
characters to the console, which is good but I still have one of the original
problems: I can only step through the code using the BDM debugger, but when I
run the code, it generates a software emulation exception and stops.

After some investigation, it seems that I can run the code up to the point
where the instructure cache is enabled - actually only a few lines at the top
of the startup code. My question is: are there any restrictions on when the
cache can be enabled? Are there anything else I've missed.

Thanks,
Daniel


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-23  7:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-19  4:31 Porting LinuxPPC Daniel Wu
2000-05-19  5:10 ` Graham Stoney
2000-05-19  8:09   ` Daniel Wu
2000-05-19  8:19     ` Graham Stoney
2000-05-19 11:07       ` Dan A. Dickey
2000-05-19 12:57   ` Daris A Nevil
2000-05-19 13:09     ` Ralph Blach
2000-05-19 15:50       ` Dan Malek
2000-05-23  7:18         ` Daniel Wu [this message]
2000-05-23 21:01           ` Richard Hendricks
2000-05-23 22:00             ` Richard Hendricks
     [not found]         ` <392A3147.3A9AC5C2@alcatel.com.au>
2000-05-30  7:49           ` Daniel Wu
2000-05-30 18:54             ` Tom Roberts
2000-05-19 11:39 ` Ralph Blach

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=00May23.171838est.115222@border.alcanet.com.au \
    --to=daniel.wu@alcatel$(echo .)com.au \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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