linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tobler <toa@pop.agri.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
	paulus@linuxcare.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC should not use -fno-builtin (was Re: 2.3.47 imac build?)
Date: Wed, 01 Mar 2000 00:07:39 +0100	[thread overview]
Message-ID: <38BC513A.9893292D@pop.agri.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10002292018001.5514-100000@opal.biophys.uni-duesseldorf.de




Michael Schmitz wrote:
>
> > >The way it fails booting is a bit entertaining: using BootX 1.1.3, it will
> > >show a little more than half a page of messages (arch_exit or similar in
> > >the last), then starts drawing funny color fringes on the screen until I
> > >reset. Using BootX 1.2b3, it locks up after the first six or so lines of
> > >text (before getting to the early console output). 2.3.29 worked fine. Any
> > >ideas?
> >
> > I think I know what's going on:
> >
> >  - make sure setting the display BAT in arch/ppc/mm/init.c (MMU_Init) is
> > commented out, this is a hack and need some alignement tricks to work in
> > all cases. It should already be in #if 0/#endif
>
> Check.
>
> >  - in arch/ppc/kernel/pmac_setup.c, comment out the content of the
> > function pmac_progress. (Or change pmac_init() so that it sets
> > ppc_md.progress to NULL, and set it to pmac_progress only pmac_setup_arch()).
>
> Tried both. I get the arch: exit if I set ppc_md.progress in pmac_setup
> arch. Shortly after this output, the color fringe fun starts again.
>
> I'll strip my .config to the bare minimum to narrow this down. Thanks for
> getting me this far :-)
Well, I wanted to reply earlier, but unfortunately my telco dropped my
line for two hours and I was thinking about having destroied my modems
until I had a look to my /var/log/messages arghhhh.

What I did: I have both trees living around on my PB. I did a diff
against the linux-pmac-devel/arch/ppc and patched the missing things. I
know a bit dangerous, but it did the trick. It's not only the things Ben
mentioned, also the drawx vs. prom_drawx are necessary I think. So it
boots on an Wallstreet I, AND on an ancient pm7200!!

I may post a patch, but I'm not quite satiesfied with since I don't know
at all what's really necessary. Sorry, but I think it's better not to
distribute a wrong patch.

Andreas

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

  reply	other threads:[~2000-02-29 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38BAF958.E31D88A3@mandrakesoft.com>
2000-02-29  0:49 ` PPC should not use -fno-builtin (was Re: 2.3.47 imac build?) Paul Mackerras
2000-02-29 17:03   ` Michael Schmitz
2000-02-29 17:51     ` Jeff Garzik
2000-02-29 18:24     ` Benjamin Herrenschmidt
2000-02-29 19:21       ` Michael Schmitz
2000-02-29 23:07         ` Andreas Tobler [this message]
2000-03-01  8:49           ` Michael Schmitz

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=38BC513A.9893292D@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com \
    --cc=schmitz@opal.biophys.uni-duesseldorf.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 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).