linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Pegasos 2 support patch ...
Date: Wed, 30 Jun 2004 10:21:50 +0200	[thread overview]
Message-ID: <20040630082150.GA23593@pegasos> (raw)
In-Reply-To: <Pine.GSO.4.58.0406301009020.20130@waterleaf.sonytel.be>


On Wed, Jun 30, 2004 at 10:10:07AM +0200, Geert Uytterhoeven wrote:
> On Wed, 30 Jun 2004, Sven Luther wrote:
> > On Tue, Jun 29, 2004 at 09:57:29PM -0500, Benjamin Herrenschmidt wrote:
> > > > Another solution would be to test before doing the translate call, maybe
> > > > this would be more elegant ?
> > >
> > > Yup, if you know it will be broken, don't bother calling it,
> > > and please, avoid the over-long line :)
> >
> > Ok, this is then the final patch, i hope it is now correct.
>
> > --- kernel-source-2.6.7.orig/arch/ppc/syslib/prom_init.c	2004-06-16 07:20:24.000000000 +0200
> > +++ kernel-source-2.6.7.peg2/arch/ppc/syslib/prom_init.c	2004-06-30 07:51:49.975232432 +0200
> > @@ -850,11 +853,20 @@
> >
> >  	klimit = (char *) (mem - offset);
> >
> > -	/* If we are already running at 0xc0000000, we assume we were
> > -	 * loaded by an OF bootloader which did set a BAT for us.
> > -	 * This breaks OF translate so we force phys to be 0.
> > -	 */
> > -	if (offset == 0) {
> > +	node = call_prom("finddevice", 1, 1, "/");
> > +	rc = call_prom("getprop", 4, 1, node, "model", model, sizeof(model));
> > +	if (rc > 0 && !strncmp (model, "Pegasos", 7)
> > +		&& strncmp (model, "Pegasos2", 8)) {
> > +		/* Pegasos 1 has a broken translate method in the OF,
> > +		 * and furthermore the BATs are mapped 1:1 so the phys
> > +		 * address calculated above is * correct, so let's use
>                                                ^
> Bogus asterisk

Ok, i will remove it thanks.

Friendly,

Sven Luther

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

  reply	other threads:[~2004-06-30  8:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 16:50 Pegasos 2 support patch Sven Luther
2004-06-29 20:42 ` Sven Luther
2004-06-30  2:57   ` Benjamin Herrenschmidt
2004-06-30  6:00     ` Sven Luther
2004-06-30  8:10       ` Geert Uytterhoeven
2004-06-30  8:21         ` Sven Luther [this message]
2004-06-30  9:18 ` Adrian Cox
2004-06-30  9:30   ` Sven Luther
2004-06-30  9:40     ` Adrian Cox
2004-06-30  9:45       ` Sven Luther
2004-06-30 15:50   ` Sven Luther
2004-06-30 16:12     ` Adrian Cox
2004-06-30 16:23       ` Sven Luther
2004-06-30 16:39         ` Adrian Cox
2004-06-30 18:52           ` Sven Luther
2004-06-30 19:05             ` Adrian Cox
2004-06-30 19:38               ` Sven Luther
2004-07-01  7:59                 ` Geert Uytterhoeven
2004-07-01  8:42                   ` Adrian Cox
2004-07-01  8:48                     ` Geert Uytterhoeven
2004-07-01  8:57                     ` Sven Luther

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=20040630082150.GA23593@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.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).