linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lee Nipper <lee.nipper@gmail.com>
To: Marc Chidester <marcchidester@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 405EX Rev D mis-identification?
Date: Thu, 8 Jul 2010 11:01:11 -0500	[thread overview]
Message-ID: <AANLkTim8xuZSaDHyxRVqk63PTT66rrR8hUhEDeNzfmKD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikrUvEicL1DaeLz9Vr-lE_hkKZqJi_7qzERZMu8@mail.gmail.com>

On Thu, Jul 8, 2010 at 10:06, Marc Chidester <marcchidester@gmail.com> wrot=
e:
> It looks like the Rev D version of the 405EX chip without security
> will be identified as a 405EXr, based on the values in the cpu_specs
> table. =A0For 405EX/405EXr the pvr_mask is =A00xffff0004 with the
> pvr_value's as 0x12910004 and 0x12910000 respectively. I see that the
> Rev D PVR value for the 405EX without security is 0x12911473, which
> would mask out to the EXr value.
>
> Is there an algorithm update needed or am I missing something?

With 405EX Rev D, we have noticed that we must reset our board
one time after the initial powerup to make the PVR read correctly.

See this post:
http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/079099.html

  reply	other threads:[~2010-07-08 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 15:06 405EX Rev D mis-identification? Marc Chidester
2010-07-08 16:01 ` Lee Nipper [this message]
2010-07-08 18:24   ` Josh Boyer
2010-07-08 18:54     ` Lee Nipper
2010-07-08 19:56     ` Marc Chidester
2010-07-08 17:59 ` Lee Nipper
2010-07-08 18:22   ` Josh Boyer
2010-07-08 19:04     ` Lee Nipper

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=AANLkTim8xuZSaDHyxRVqk63PTT66rrR8hUhEDeNzfmKD@mail.gmail.com \
    --to=lee.nipper@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marcchidester@gmail.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).