linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on PPC
Date: Fri, 03 Mar 2006 09:33:24 +0000	[thread overview]
Message-ID: <1141378405.8912.31.camel@localhost.localdomain> (raw)
In-Reply-To: <4407CFD3.4060206@ovro.caltech.edu>

On Thu, 2006-03-02 at 21:10 -0800, David Hawkins wrote:
> Step 2. Find a PPC 750 port in the Linux source.
> 
>       For example, in the 2.6 series kernel, the place to start
>       looking is under arch/ppc/platforms. grep -Ie 750 shows
>       up some of the PPC 750 based systems.
> 
>       chestnut.c 750FX/GX evaluation board
>       katana.c   Looks like one too
>       prpmc750.c Looks like a Motorola board
> 
>       Look at the comments in the code, look at the memory map
>       of the reference board versus your custom board. There is
>       a very good chance that the custom board is based on a
>       reference design - thats the whole point of them.

I'd add the caution that within the 6xx, 7xx, and 7xxx family of
processors, the north-bridge makes a much greater difference than the
processor core. Within that family of processors Linux will auto-detect
the processor specific features at boot time. It will be easier to port
from a board using a 7450 with the same north-bridge, than from a board
using a 750 with a different north-bridge.

-- 
Adrian Cox <adrian@humboldt.co.uk>

  reply	other threads:[~2006-03-03  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03  2:01 Linux on PPC rtos
2006-03-03  2:23 ` Frank
2006-03-03  5:09 ` nreddy
2006-03-03 16:00   ` Wolfgang Denk
2006-03-03  5:10 ` David Hawkins
2006-03-03  9:33   ` Adrian Cox [this message]
2006-03-03 16:04   ` Wolfgang Denk
2006-03-03 16:53     ` David Hawkins
2006-03-04  2:05       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-03-03 19:39 Rune Torgersen
2006-03-03 20:06 ` David Hawkins
2006-03-04  2:09   ` Wolfgang Denk
2006-03-04  2:51     ` David Hawkins
2006-03-03 20:28 Steve Strublic
2006-03-03 20:31 Rune Torgersen

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=1141378405.8912.31.camel@localhost.localdomain \
    --to=adrian@humboldt.co.uk \
    --cc=dwh@ovro.caltech.edu \
    --cc=linuxppc-embedded@ozlabs.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 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).