linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Updegraff <dave@cray.com>
To: Stefan Roese <stefan.roese@esd-electronics.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405GPr
Date: Mon, 10 Jun 2002 08:11:13 -0500	[thread overview]
Message-ID: <3D04A571.4020309@cray.com> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJIELDEAAA.stefan.roese@esd-electronics.com


Stefan

We got one in I made some "proof of concept" changes to PPCBOOT/LinuxPPC
to make it boot ok.. have not played with the extra clocking
register strap values though; we just plopped it into our
405GP socket and ran @200 Mhz.  Worked...

I noticed that the PVR on the unit we got was a bit different:
ibm specs said
	0x50910950
..but I got
	0x50910951

Is there a doc. somewhere that tells us what the ranges of PVRs
for this chip can legitimately be?

>>>Anyone playing with adding IBM 405GPr to the cputable?
>>
>>Stephan said on the PPCboot list that he will have boards with
>>them soon. He has done patches for PPCBoot so the kernel may not
>>be far off. It will still be a couple of weeks before I get a
>>board with one yet.
>
>
> Right! As promised PPCBoot will be done next week, and linux will follow (if
> I am still the first) pretty soon.
>
> Stefan.
>
>
>



--
David Updegraff / dave@cray.com / 218.525.1154


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

  reply	other threads:[~2002-06-10 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 20:48 Ebony 440 board Brian Kuschak
2002-06-06 22:11 ` 405GPr David Updegraff
2002-06-06 23:25   ` 405GPr andrew may
2002-06-07  7:40     ` 405GPr Stefan Roese
2002-06-10 13:11       ` David Updegraff [this message]
2002-06-10 14:23         ` 405GPr Stefan Roese

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=3D04A571.4020309@cray.com \
    --to=dave@cray.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=stefan.roese@esd-electronics.com \
    /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).