From: Scott Wood <scottwood@freescale•com>
To: Olof Johansson <olof@lixom•net>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>
Subject: Re: [PATCH 1/2] [POWERPC] 4xx: Add 405EXr to cputable
Date: Tue, 15 Jan 2008 12:25:26 -0600 [thread overview]
Message-ID: <478CFA96.90009@freescale.com> (raw)
In-Reply-To: <20080115183240.GC25749@lixom.net>
Olof Johansson wrote:
> On Tue, Jan 15, 2008 at 12:19:24PM -0600, Scott Wood wrote:
>> On Tue, Jan 15, 2008 at 08:09:15AM +0100, Stefan Roese wrote:
>>> This patch adds the 405EXr to the powerpc cuptable. Basically the 405EXr
>>> is a 405EX with only one EMAC and only one PCIe interface.
>> Sounds like they have the same core... why do they need separate cputable
>> entries?
>
> AMCC has always indicated SoC products by new PVRs. This isn't news,
> even though it isn't exactly a clean solution. :)
But the old 405EX entry would have matched both chips. Why add a new
significant bit to pvr_mask? For the name in /proc/cpuinfo?
-Scott
next prev parent reply other threads:[~2008-01-15 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 7:09 [PATCH 1/2] [POWERPC] 4xx: Add 405EXr to cputable Stefan Roese
2008-01-15 18:19 ` Scott Wood
2008-01-15 18:32 ` Olof Johansson
2008-01-15 18:25 ` Scott Wood [this message]
2008-01-15 18:38 ` Olof Johansson
2008-01-15 18:47 ` Josh Boyer
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=478CFA96.90009@freescale.com \
--to=scottwood@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=olof@lixom$(echo .)net \
--cc=sr@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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