public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: "Patrick Huesmann" <tricknology@gmx•de>
To: "Peter 'p2' De Schrijver" <p2@mind•be>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: How to port ppc-linux to new custom boards? (virtexII)
Date: Tue, 24 Aug 2004 11:14:35 +0200 (MEST)	[thread overview]
Message-ID: <27642.1093338875@www70.gmx.net> (raw)
In-Reply-To: 20040824085118.GO2698@mind.be


Hi,

> A lot of the 405 specific kernel code relies on the
> fact that main memory is mapped at address 0. It would require quite
> some work to make it work on other addresses too.

You mean that RAM has to start at *physical* address zero? Well, then
perhaps I can convince the hardware guy to change the memory layout. It's a
softcore SDRAM controller, after all ;))

> > Where does my board specific fixup stuff go
> > (for
> > example, memory and IRQ declarations and such).
>
> Most of the board specific fixup stuff resides in
> platforms/boardname.[ch]. Look at arch/ppc/platforms/insightv2pro.[ch]
> for an example how we did this for the insight V2Pro board.

Thanks for the suggestions. I'll be looking into that, once I've handled the
low-level stuff.

> > 2) What requirements and responsibilities are imposed on the bootloader?
>
> The bootloader should load the kernel at address 0 and initialize the
> registers as follows (...)
> (See also arch/ppc/kernel/head_4xx.S). The board info structure is
> defined in asm-ppc/ppcboot.h (struct bd_info).

Thanks, I've already seen that one. Are there any other requirements (cache
flushing, cache turned on/off, interrupts disabled, etc.)?

> > 3) Is there a way to get a self-decompressing kernel image?
>
> Yes. look at arc/ppc/boot/simple for some targets which have a
> self-decompressing kernel. (Amongst which is our port to the Insight
> V2PRO board).

Hmm. The denx tutorial states that the bootloader *must* decompress the
kernel. If that's not true (anymore), then I might not have to use u-boot as
second stage bootloader.

Thanks,
Patrick


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

next prev parent reply	other threads:[~2004-08-24  9:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 15:17 How to port ppc-linux to new custom boards? (virtexII) Patrick Huesmann
2004-08-24  1:30 ` Song Sam
2004-08-24  4:14 ` Peter Ryser
2004-08-24  8:51 ` Peter 'p2' De Schrijver
2004-08-24  9:14   ` Patrick Huesmann [this message]
2004-08-24  9:42     ` Peter 'p2' De Schrijver
2004-08-24 10:01     ` Song Sam
2004-08-25  2:00   ` Song Sam
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24  6:27 Patrick Huesmann
2004-08-24  7:25 ` Marc Leeman
2004-08-25  7:34   ` Marius Groeger
2004-08-25  7:57     ` Marc Leeman
2004-08-25 13:52     ` David Ho
2004-08-25 14:30       ` Peter Vandenabeele
2004-08-26  7:02         ` Marc Leeman
2004-08-24  8:01 ` Oliver Fuchs
2004-08-24  8:31 ` Peter Ryser
     [not found] <31481.1093602240@www36.gmx.net>
2004-08-27 11:18 ` Patrick Huesmann

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=27642.1093338875@www70.gmx.net \
    --to=tricknology@gmx$(echo .)de \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=p2@mind$(echo .)be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox