linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, Roland Dreier <rdreier@cisco.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC/PATCH] Change 440GP platform to ppc440
Date: Tue, 1 May 2007 22:38:29 -0500	[thread overview]
Message-ID: <E98E4E57-2322-412F-A58E-A0CCC39DDCE3@kernel.crashing.org> (raw)
In-Reply-To: <200704240746.05129.sr@denx.de>


On Apr 24, 2007, at 12:46 AM, Stefan Roese wrote:

> On Tuesday 24 April 2007 02:12, Roland Dreier wrote:
>>>> I recall dimly that there was some user-visible difference  
>>>> between the
>>>> 440GP and the other 440 processors, and that's why we made the
>>>> platform string different.  I don't recall what the difference was.
>>
>> FWIW, I've run the same userspace (binaries) on 405GPr, 440GP and
>> 440SPe without any problems.  Not that I'm a 4xx expert by any
>> stretch, but I don't know of anything special about the 440GP.
>
> I don't know of any differences either. So I'm voting to change the  
> platform
> to ppc440 too.

After some discussion with Paul we think we figured out why 440GP was  
marked differently.  I doesn't implement 'isel', and all other 440's do.

- k

  reply	other threads:[~2007-05-02  3:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 21:16 [RFC/PATCH] Change 440GP platform to ppc440 Kumar Gala
2007-04-19 21:43 ` Josh Boyer
2007-04-20  0:02   ` David Gibson
2007-04-21  0:20 ` Paul Mackerras
2007-04-23 21:58   ` Kumar Gala
2007-04-24  0:01     ` Josh Boyer
2007-04-24  0:12       ` Roland Dreier
2007-04-24  5:46         ` Stefan Roese
2007-05-02  3:38           ` Kumar Gala [this message]
2007-05-02 14:06             ` What defines a cpu table platform? (was Re: Change 440GP platform to ppc440) Kumar Gala

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=E98E4E57-2322-412F-A58E-A0CCC39DDCE3@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=rdreier@cisco.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;
as well as URLs for NNTP newsgroup(s).