linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank McPherson <frank@mitre.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: xmon, BAT structure, etc.
Date: Mon, 25 Jan 1999 16:10:12 -0500	[thread overview]
Message-ID: <36ACDDB2.6DA8ACA7@mitre.org> (raw)


xmon doesn't seem to exist in the linuxppc sources any more and I'm
having trouble getting the one from the linuxppc.org 2.1.24 sources to
compile with 2.2.0-pre5, which is the latest version I was able to pull
from vger's anonymous cvs before it started always refusing connections.
  Where can I get it, or something equivalent?  What's the best way to
debug the platform-specific code that's run shortly after the
bootloader?  

I'm working on getting linux up and running on a non-prep, non-pci VME
board with a 603e and having some trouble with it.  I've got the kernel
uncompressing down to where it should be, but it traps when it gets a
bit of the way in to init/main.c.  When I write the contents of the BAT
structure to dual port RAM on the VME bus, I get all zeros, leading me
to believe I'm not setting thins up correctly down in the
platform-specific sections.  

Thanks,

Frank

-- 
Frank H. McPherson IV
The MITRE Corporation

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

             reply	other threads:[~1999-01-25 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-25 21:10 Frank McPherson [this message]
1999-02-02  5:29 ` xmon, BAT structure, etc Paul Mackerras

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=36ACDDB2.6DA8ACA7@mitre.org \
    --to=frank@mitre.org \
    --cc=linuxppc-dev@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).