linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tony Mantler <eek@escape.ca>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Performa 5200
Date: Tue, 24 Aug 1999 11:06:02 +0200	[thread overview]
Message-ID: <19990824110602.000653@mail.mipsys.com> (raw)
In-Reply-To: <v04003a04b3e7e12ecd82@[216.81.20.86]>


On Tue, Aug 24, 1999, Tony Mantler <eek@escape.ca> wrote:

>I recently obtained for myself up a Performa 5200, and I've been playing
>with trying to hack linux into shape on it. (I'm usually a Mac68k guy)
>
>I compiled a kernel from a stock 2.2.10 tree that I have laying around
>(from ftp.kernel.org, most every config option turned off, booting with
>BootX) and, after sprinkling around a bit of debug code, found that it
>makes it past the prom.c code where it draws the "Welcome to linux
>[blahblah] booting...", but doesn't make it to start_kernel after that.
>
>I'm not particularily fluent in PPC ASM, so head.S makes fairly opaque
>reading for me. I'm wondering if someone might have some pointers to where
>this would likely be dying, so I have good a place to start?

is this a NuBus class machine or a PCI based one ? If it's a NuBus one,
then you are out of luck, or if you have time to spend, you can begin
porting linux/ppc to those beasts. (Basically, RAM is not contiguous and
you cannot rely in the kernel beeing loaded at physical 0, since the
frame buffer may be hard coded at physical 1Mb). Look at the various
parameters BootX pass for a NuBus machine (using the latest 2.1.12 kernel
from vger or Paul's rsync, you should have the latest bootx.h).


-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-08-24  9:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-24  5:59 Performa 5200 Tony Mantler
1999-08-24  9:06 ` Benjamin Herrenschmidt [this message]
1999-08-24 13:29   ` Dave Weis
1999-08-24 18:05     ` David A. Gatwood
1999-08-24 21:21   ` Tony Mantler
1999-08-25 10:23     ` Benjamin Herrenschmidt
1999-08-25 19:59       ` Tony Mantler
1999-08-26  3:43         ` David A. Gatwood
1999-08-26  4:15           ` Tony Mantler
1999-08-26  4:38             ` David A. Gatwood
1999-08-26  6:41               ` Tony Mantler
1999-08-26  8:57                 ` Benjamin Herrenschmidt
1999-08-26 18:11                 ` David A. Gatwood
1999-08-26  8:44         ` Benjamin Herrenschmidt
1999-08-26  3:45       ` David A. Gatwood
1999-08-26  8:53         ` Benjamin Herrenschmidt
1999-08-26  8:01       ` Geert Uytterhoeven
1999-08-25 10:36   ` Hubert Figuiere
1999-08-26  8:03     ` Geert Uytterhoeven
1999-08-26  8:59       ` Benjamin Herrenschmidt
1999-08-24 17:38 ` David A. Gatwood
  -- strict thread matches above, loose matches on Subject: below --
1999-08-26  8:52 Benjamin Herrenschmidt

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=19990824110602.000653@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=eek@escape.ca \
    --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).