linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul White <pwhite@bivio.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC7455
Date: Wed, 6 Mar 2002 21:59:56 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0203062152510.30207-100000@stimpy.networkrobots.com> (raw)
In-Reply-To: <20020306194635.11178@smtp.wanadoo.fr>


On Wed, 6 Mar 2002, Benjamin Herrenschmidt wrote:

> Please, send them to me. I have some 7455 support in my rsync tree
> that I am about to push to bk. However, some of the registers, like
> HID1 or MSSCR0, I consider have to be setup by the firmware or by
> machine specific code.

Yes - It seems this is what Linux expects for the 7450 as well,
as it requests the firmware setup the CPU.

In my 7455 setup, I setup the CPU in linux, assuming the firmware
hasn't done anything yet.  Things such as Address Broadcast Enable
bits are now in HID1 instead of HID0 as on other processors.  As
for cache snooping, the 7455 defaults to a different method of
External Data Intervention.  Maybe this is something firmware
usually sets up?  Using the Galileo system controller, we had to
disable this mode to make it compatable to the MPC7410.

> >Store Instruction
> >Load Instruction
> > - This is not guarenteed in order, even if its Guarded
>
> Ah ? I missed that in the doc. It's pretty bad though so far, all
> drivers are supposed to eieio on any IO access anyway.

See section 3.3.3.5, page 3-29 of the 7450/7455 Users manual..  Its
good that everything already does eieio's between IO accesses.  We
(being our driver engineers here) are kicking ourselves for not
adding these into our custom drivers.  We've added them now, and
things seem to work great!

> My current tree boots and appear to work on Apple dual G4 1Ghz which is
> 7455 based.
>
> I'm still interested in your patches as I may have missed something.

Great!  It sounds like the firmware is doing everyhting.  It might be
nice to add an option to have linux configure the CPU registers or not,
as for us embedded guys thats easier than implimenting it all in the
firmware.  We can do it either way now that we know what the registers
should be, though.

I'll have a cleaned up patch file by tomorrow evening.  What tree
would you prefer the patch be against?

Paul W.


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

  reply	other threads:[~2002-03-07  5:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  7:02 MPC7455 Paul White
2002-03-06 19:46 ` MPC7455 Benjamin Herrenschmidt
2002-03-07  5:59   ` Paul White [this message]
2002-03-06 21:48     ` MPC7455 benh
2002-03-07 15:30       ` MPC7455 Tom Rini
2002-03-07 16:45         ` MPC7455 Dan Malek
2002-03-07  9:24   ` MPC7455 Gabriel Paubert
2002-03-06 22:18 ` MPC7455 Kevin B. Hendricks
2002-03-07  6:01   ` MPC7455 Paul White
2002-03-07  8:41 ` MPC7455 Giuliano Pochini

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=Pine.LNX.4.21.0203062152510.30207-100000@stimpy.networkrobots.com \
    --to=pwhite@bivio.net \
    --cc=benh@kernel.crashing.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).