linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: "Wood, Robert \(GE EntSol,
	Intelligent Platforms\)" <robert.wood@gefanuc.com>,
	Linuxppc-embedded@ozlabs.org
Subject: Re: powerpc405 versus powerpc440
Date: Wed, 17 Sep 2008 02:25:28 -0700	[thread overview]
Message-ID: <20080917092528.GA7572@secretlab.ca> (raw)
In-Reply-To: <20080904150725.GE2479@yoda.jdub.homelinux.org>

On Thu, Sep 04, 2008 at 11:07:25AM -0400, Josh Boyer wrote:
> On Thu, Sep 04, 2008 at 09:28:01AM -0400, Wood, Robert (GE EntSol, Intelligent Platforms) wrote:
> >We are migrating to the Xilinx Virtex 5 devices and that means migrating
> >our embedded software from the PowerPC405 to PowerPC440.
> >
> >Are there any gotchas we should be aware of, or will this be simple case
> >of S/W migration :-)
> 
> Erm.  405 and 440 have entirely different MMUs.  405 has real-mode, and 440
> is BookE and therefore has the MMU always on.
> 
> That is mostly an impact to the kernel itself and not to userspace.  But it
> can be annoying if you aren't used to dealing with BookE style CPUs.

As Josh said, the MMUs are entirely different, but it is mostly isolated
to impacting the kernel.  The mainline kernel already has basic support
for the Virtex5 440 in the latest release.  Also, the xilinx git server
(git.xilinx.com) has a tree with drivers for a bunch of the xilinx
devices that aren't quite ready for mainline yet.

g.

  reply	other threads:[~2008-09-17  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 14:10 Boot 2.6.26 (or similar) on mpc5200 using powerpc Angelo
2008-09-04 12:05 ` Detlev Zundel
2008-09-04 13:08   ` Angelo
2008-09-04 13:28     ` powerpc405 versus powerpc440 Wood, Robert (GE EntSol, Intelligent Platforms)
2008-09-04 15:07       ` Josh Boyer
2008-09-17  9:25         ` Grant Likely [this message]
2008-09-04 14:47     ` Boot 2.6.26 (or similar) on mpc5200 using powerpc Detlev Zundel

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=20080917092528.GA7572@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=robert.wood@gefanuc.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).