From: "Patrick Huesmann" <tricknology@gmx.de>
To: "Oliver Fuchs" <olivers.lists@gmx.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: How to port ppc-linux to new custom boards? (virtexII)
Date: Fri, 27 Aug 2004 13:18:51 +0200 (MEST) [thread overview]
Message-ID: <10733.1093605531@www29.gmx.net> (raw)
In-Reply-To: 31481.1093602240@www36.gmx.net
Hi,
> > Thank you very much. This is exactly the type of info I'm looking for.
> > Did you manage to get a self-decompressing zImage, or is this ALWAYS the
> > bootloader's job on ppc-linux?
> I guess in my case (U-Boot) it is the job of the bootloader.
> May be you have to add the decompressing code to your bootloader.
> This seems to be not so complicated for the code is available.
> Download the U-Boot sources and look for the function gunzip() within
> common/cmd_bootm.c
In the meantime, I managed to build a self-decompressing zImage. It is
fairly easy, the board type has to be added to the arch/ppc/boot/simple
Makefile and the zImage is then generated by using dd to strip the ELF
headers off the zvmlinux file. (There are already examples for this in the
Makefile).
BTW: The zImage is *MANDATORY* if there is no standard bootloader used,
because embed_config() sets up the board info structure and sets up some
essential magic cache stuff. I spent a few days just messing around,
wondering why I got strange errors and unreproducable behaviour. Eventually,
I found out that the cache was b0rken because I didn't do the initial cache
setup thing ;)
Thanks again to all folks who replied to my thread,
Patrick
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-08-27 11:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31481.1093602240@www36.gmx.net>
2004-08-27 11:18 ` Patrick Huesmann [this message]
2004-08-24 6:27 How to port ppc-linux to new custom boards? (virtexII) 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
-- 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=10733.1093605531@www29.gmx.net \
--to=tricknology@gmx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=olivers.lists@gmx.net \
/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.