From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Scott Wood <scottwood@freescale.com>,
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:47:29 -0600 [thread overview]
Message-ID: <20080115124729.779f4c0d@zod.rchland.ibm.com> (raw)
In-Reply-To: <20080115183809.GD25749@lixom.net>
On Tue, 15 Jan 2008 12:38:09 -0600
Olof Johansson <olof@lixom.net> wrote:
> On Tue, Jan 15, 2008 at 12:25:26PM -0600, Scott Wood wrote:
> > 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?
>
> Presumably, yes.
>
> Again, this is nothing new. Other 405/440 products are doing the same
> thing.
Does anyone have an actual problem with this patch? I'm inclined to
take it as it doesn't really cause any problems and may eventually be
needed anyway if there is a chip errata or something.
josh
prev parent reply other threads:[~2008-01-15 18:48 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
2008-01-15 18:38 ` Olof Johansson
2008-01-15 18:47 ` Josh Boyer [this message]
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=20080115124729.779f4c0d@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=scottwood@freescale.com \
--cc=sr@denx.de \
/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