All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Johan Borkhuis <j.borkhuis@dutchspace.nl>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: arm and ppc plattforms
Date: Fri, 20 Apr 2007 18:02:30 +0200	[thread overview]
Message-ID: <4628E416.7050003@grandegger.com> (raw)
In-Reply-To: <4628C75F.1080407@dutchspace.nl>

Johan Borkhuis wrote:
> Robert Schwebel wrote:
>> You'll probably have no luck with ARCH=ppc, our port runs with
>> ARCH=powerpc (and still has some crude hacks inside).   
> I am in the same situation: I have a board (MVME3100, PPC8540) that uses 
> the ARCH=ppc, but I have some strict realtime requirements. As far as I 
> understand from the discussions on this list (and on other places) the 
> ARCH=ppc will be dropped in favor of ARCH=powerpc, and the -rt patch 
> will not support the ppc-architecture.

Not dropped but almost frozen. Already today there is little interest in 
maintaining the ppc tree. And for real-time preemption and the 
high-resolution timers the generic IRQ and timer layer seems now 
mandatory, which is not available for ppc. What is mainly missing for 
PowerPC is the support of clock events to get the high-resolution timers 
working.
Pengutronix has a temporary solution for that. See Robert's mail:

http://www.mail-archive.com/linux-rt-users@vger.kernel.org/msg00343.html

> But before I start working on the powerpc-version of the BSP I would 
> like to know how stable the patch runs on powerpc (and specifically on 
> ppc85xx), and how good the realtime performance of the patch is on 
> powerpc. Are there any (recent) performance measurements available for 
> the patch on a powerpc platform?

I think MPC 85xx is well supported and in arch/powerpc/configs there are 
already a few MPC85xx boards available.

> Also a question that is not directly related to this list, but maybe 
> someone can help me with it. Is there some information available on 
> porting a BSP from ppc to powerpc? I was not able to find information on 
> this except for the fact that the ppc architecture will be dropped, but 
> no information on what impact this has on a BSP.

Unfortunately, porting takes some effort, especially because of the 
mandatory Open Firmware flattened device tree (DTF). Please read 
Documentation/powerpc/booting-without-of.txt for further information. 
But there are already examples for the MPC85xx. There are more new 
things like the generic IRQ and timer layer, but that should be already 
available for your boards. For more details, please ask on the 
linuxppc-embedded ML.

Wolfgang.

  reply	other threads:[~2007-04-20 15:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 10:56 arm and ppc plattforms Peter Feuerer
2007-04-20 11:08 ` Robert Schwebel
2007-04-20 11:17   ` Peter Feuerer
2007-04-20 11:23   ` Pradyumna Sampath
2007-04-20 11:34     ` Robert Schwebel
2007-04-20 13:59       ` Johan Borkhuis
2007-04-20 16:02         ` Wolfgang Grandegger [this message]
2007-04-20 16:01   ` Theodore Tso
2007-04-20 16:40     ` Robert Schwebel

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=4628E416.7050003@grandegger.com \
    --to=wg@grandegger.com \
    --cc=j.borkhuis@dutchspace.nl \
    --cc=linux-rt-users@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.