All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Huesmann" <tricknology@gmx.de>
To: linuxppc-embedded@lists.linuxppc.org
Cc: samlinuxppc@yahoo.com.cn
Subject: Re: How to port ppc-linux to new custom boards? (virtexII)
Date: Tue, 24 Aug 2004 08:27:03 +0200 (MEST)	[thread overview]
Message-ID: <18802.1093328823@www32.gmx.net> (raw)


Hi,

> Where did you download the Montavista 2_4_devel?

via anonymous rsync from montavista server. i followed the instructions at
http://penguinppc.org/dev/kernel.shtml

>> 1) Is there any comprehensive documentation / tutorial on how to port
>> the ppc-linux to new machines? Where does my board specific fixup
>> stuff go (for example, memory and IRQ declarations and such).
>
>See the following two valuable docs:
>http://www.denx.de/twiki/bin/view/PPCEmbedded/Introduction
>http://www.denx.de/twiki/bin/view/DULG/Manual

Unfortunately, neither of these docs talks about tailoring the kernel to
custom hardware. They only state that "some changes" have to be applied to
the startup code. I need some more specific information, because I'm not a
expert PPC guru.

>> vmlinux file and write it to flash directly, because zImage on powerpc
>> lacks decompressor code (at least with my configuration). But the
>> 1.3meg vmlinux file makes for pretty long turnaround times (I can only
>> upload at 115k at the moment).
>
>AFAIK, the key point of decompressing is boot loader
>itself. It has NOTHING to do with ppc linux. Both
>U-Boot and PlanetCore can do this job well.

this means that i also have to port u-boot and use 2 bootloaders in
sequence, or port u-boot's decompressor code to our own bootloader. Sigh.

Arm Linux provides a self-decompressing zImage. I thought it could be
possible to configure the ppc kernel just like that.

Thanx anyway,
Patrick


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

             reply	other threads:[~2004-08-24  6:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  6:27 Patrick Huesmann [this message]
2004-08-24  7:25 ` How to port ppc-linux to new custom boards? (virtexII) 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-25 20:08         ` Handling of cascaded interrupt controllers Jeff Domogala
2004-08-26  7:02         ` How to port ppc-linux to new custom boards? (virtexII) 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
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 15:17 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
2004-08-24  9:42     ` Peter 'p2' De Schrijver
2004-08-24 10:01     ` Song Sam
2004-08-25  2:00   ` Song Sam

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=18802.1093328823@www32.gmx.net \
    --to=tricknology@gmx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /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.