From: Gabriel Paubert <paubert@iram.es>
To: Chris Studholme <cvs@cs.utoronto.ca>
Cc: linuxppc-dev@lists.linuxppc.org,
Terry Greeniaus <tgree@phys.ualberta.ca>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: pismo upgraded to 750fx not detected correctly
Date: Tue, 24 Jun 2003 10:18:29 +0200 [thread overview]
Message-ID: <20030624081829.GA30884@iram.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0306231306590.5151-100000@stoa.dhs.org>
On Mon, Jun 23, 2003 at 01:16:41PM -0400, Chris Studholme wrote:
> On Mon, 23 Jun 2003, Gabriel Paubert wrote:
> > > diff -c -r linux-2.4.21-ac1.orig/arch/ppc/kernel/misc.S linux-2.4.21-ac1/arch/ppc/kernel/misc.S
> > > *** linux-2.4.21-ac1.orig/arch/ppc/kernel/misc.S Fri Jun 13 10:51:31 2003
> > > --- linux-2.4.21-ac1/arch/ppc/kernel/misc.S Sun Jun 22 21:25:32 2003
> > > ***************
> > > *** 113,118 ****
> > > --- 113,139 ----
> > > addis r8,r3,cpu_specs@ha
> > > addi r8,r8,cpu_specs@l
> > > mfpvr r7
> > > +
> > > + /* check for 750fx strapped on as 750 */
> > > + srwi r6,r7,16
> > > + cmpli 0,r6,8
> > > + bne 1f
> > > + mfspr r5,0x3F1
> > > + srwi. r6,r5,17
> > > + bso 2f
> >
> > Are you sure you want to test the summary overflow bit
> > in this branch ? This bit is not related to the result
> > of the preceding srwi. instruction, so this looks
> > strange to say the least.
>
> What I was trying to do is test the last bit shifted out by the srwi., but
> I still don't know how to do that, so how about this instead:
>
> mfspr r5,0x3F1
> andis. r6,r5,0x0001
> bne 2f
This looks much better, and is the standard way
of testing a bit on PPC.
> > > slwi r4,r4,2
> > > sub r8,r8,r3
> > > stwx r8,r4,r6
> > > +
> > > + addis r6,r3,real_pvr@ha
> > > + addi r6,r6,real_pvr@l
> > > + stwx r7,0,r6
> >
> > A bit convoluted no? r3 is supposed to be zero, so
Argh, disregard this. I've been lately working too much with
an assembler in which the result is the last operand and
believed that sub r8,r8,r3 was a convoluted way of clearung r3.
> > the standard way of performing this is:
> > lis r6,real_pvr@ha
> > stw r7,real_pvr@l(r6)
>
> I believe when this method is called, there is some concern over where
> data is. The method comments are:
>
> /*
> * identify_cpu,
> * called with r3 = data offset and r4 = CPU number
> * doesn't change r3
> */
>
> and all of the other references to global data involve r3, like:
>
> addis r8,r3,cpu_specs@ha
> addi r8,r8,cpu_specs@l
>
> and
>
> addis r6,r3,cur_cpu_spec@ha
> addi r6,r6,cur_cpu_spec@l
> slwi r4,r4,2
> sub r8,r8,r3
> stwx r8,r4,r6
>
> so I figured I should do the same. But perhaps I could still simplify my
> code with:
>
> addis r6,r3,real_pvr@ha
> stwx r7,real_pvr@l(r6)
Correct, provided the last instruction is stw instead of stwx, and
unless I miss again something.
Gabriel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-24 8:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200306200459.XAA31217@lists.linuxppc.org>
2003-06-20 5:53 ` pismo upgraded to 750fx not detected correctly Terry Greeniaus
2003-06-21 15:58 ` Chris Studholme
2003-06-22 9:49 ` Benjamin Herrenschmidt
2003-06-22 21:58 ` Terry Greeniaus
2003-06-23 6:01 ` Benjamin Herrenschmidt
2003-06-23 4:47 ` Chris Studholme
2003-06-23 8:27 ` Gabriel Paubert
2003-06-23 17:16 ` Chris Studholme
2003-06-24 8:18 ` Gabriel Paubert [this message]
2003-06-23 17:46 ` Benjamin Herrenschmidt
2003-06-26 17:02 ` how to setup PLL1 on 750FX Chris Studholme
2003-06-26 17:33 ` Terry Greeniaus
2003-06-26 20:47 ` Chris Studholme
2003-06-27 11:37 ` Benjamin Herrenschmidt
2003-06-28 3:05 ` Chris Studholme
2003-06-28 8:23 ` Benjamin Herrenschmidt
2003-06-30 18:57 ` Chris Studholme
2003-07-01 9:52 ` Benjamin Herrenschmidt
[not found] <200306130459.XAA18908@lists.linuxppc.org>
2003-06-13 5:44 ` pismo upgraded to 750fx not detected correctly Terry Greeniaus
2003-06-19 18:18 ` Chris Studholme
2003-06-12 20:05 Chris Studholme
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=20030624081829.GA30884@iram.es \
--to=paubert@iram.es \
--cc=benh@kernel.crashing.org \
--cc=cvs@cs.utoronto.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tgree@phys.ualberta.ca \
/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).