All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan A. Dickey" <ddickey@charter.net>
To: Nicolas-Peter Pohland <pohland@snom.de>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: How to get rom code to go on FADS?
Date: Tue, 16 May 2000 21:31:10 -0500	[thread overview]
Message-ID: <3922046E.D77E156@charter.net> (raw)
In-Reply-To: 3921B844.572E3C63@charter.net


"Dan A. Dickey" wrote:
>
> Nicolas-Peter Pohland wrote:
> >
> > Did you try "rms der 0" (assuming you have the ADI board and MPC8bug SW)
>
> Nope, haven't tried that.  I'll look at it later tonight; thanks
> for the tip.

Good!  Fantastic tip.
This helps tremendously, especially in the fact that now I can
actually boot and run the kernel on my fads... while the ADI &
mpc8bug are connected.  Before that, I would always get the
InstructionTLBMiss exception - and of course, mpc8bug didn't
really know anything about the address.

Also, I'm also now running in "stand alone" mode - with the
ADI & mpc8bug disconnected.  Straight from the flash.

For me, this is great news.  I know that most of you don't
give a hoot!  :)

So, I'm attributing this recent success to:
	A)  Setting SYPCR in the rom code fairly early on.
	B)  Issuing a "rms der 0" to mpc8bug when it is connected.

I'm a happy camper at the moment.  Mostly.  :)
I just need to get my regular system setup to allow bootp and
host an nfs root for the fads.
Also, I just noticed - the kernel couldn't mount root, so it's
doing its "Rebooting in 180 seconds.." act.  However, about
all I'm seeing after that is a:
	<0>Kernel panic: Kernel Mode Software FPU Emulation
and then the duo is repeating every 180 seconds...
Not quite what I call a reboot.  I would think it would at
least manage to restart the rom initialization code.
Anyways, thats relatively minor...
have a good night!
	-Dan

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

  parent reply	other threads:[~2000-05-17  2:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-11 21:11 How to get rom code to go on FADS? Dan A. Dickey
2000-05-12 16:33 ` Richard Hendricks
2000-05-12 17:03   ` Dan A. Dickey
2000-05-12 18:57     ` Richard Hendricks
2000-05-13 13:54       ` Dan A. Dickey
2000-05-15 15:54         ` Richard Hendricks
2000-05-15 17:00           ` Dan A. Dickey
2000-05-15 17:43             ` Dan A. Dickey
2000-05-15 18:25               ` Dan A. Dickey
2000-05-16 14:50                 ` Richard Hendricks
2000-05-16 21:03                   ` Dan A. Dickey
2000-05-16  1:55             ` Dan A. Dickey
2000-05-16 14:45               ` Richard Hendricks
     [not found]               ` <3920ED16.A2D26629@snom.de>
     [not found]                 ` <3921B844.572E3C63@charter.net>
2000-05-17  2:31                   ` Dan A. Dickey [this message]
2000-05-17 19:08                     ` Richard Hendricks
2000-05-18  3:20                       ` Dan Malek
2000-05-18  3:22                         ` Dan A. Dickey
2000-05-18  3:20                       ` Dan A. Dickey
2000-05-18 16:15                         ` Richard Hendricks
2000-05-19 11:12                           ` Dan A. Dickey
2000-05-19 15:01                             ` Richard Hendricks
2000-05-13  5:18     ` duncanp

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=3922046E.D77E156@charter.net \
    --to=ddickey@charter.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pohland@snom.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.