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 12:59:29 -0500 [thread overview]
Message-ID: <AANLkTikCFgFZsAl0QLkZbI1Jbrh8v0d7gK9EVtqCe1QU@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> wrote:
> 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.
Yes, that is the case.
The 405EX Rev D without security PVR matches an old 405EXr A/B with security,
and hence the cpu_spec entries' pvr_mask values are no longer correct.
> Is there an algorithm update needed or am I missing something?
Perhaps add more cpu_spec table entries for the 405EX & 405EXr with
pvr_mask = 0xffff000f ?
next prev parent reply other threads:[~2010-07-08 17:59 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
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 [this message]
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=AANLkTikCFgFZsAl0QLkZbI1Jbrh8v0d7gK9EVtqCe1QU@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).