From: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
To: Tom Rini <trini@kernel.crashing.org>
Cc: luca gambazzi <luca.gambazzi@epfl.ch>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on PowerCore CPCI-3750
Date: Thu, 27 Mar 2003 21:13:24 +0100 [thread overview]
Message-ID: <3E835B64.4070103@bluewin.ch> (raw)
In-Reply-To: 20030327184853.GE31771@ip68-0-152-218.tc.ph.cox.net
On 03/27/2003 07:48 PM Tom Rini wrote:
> On Thu, Mar 27, 2003 at 02:02:28PM +0100, luca gambazzi wrote:
>
>> i'm swiss student, i'm trying to crosscompile a linux kernel for a Force
>> Computers PowerCore CPCI-3750.
> [snip]
>> so my kernel image is wrong,... to create the kernel image (v2.5 patched
>> for ppc) i've used the make bzImage and then with powerpc-linux-objcopy
>> i've changed the ELF32bit file in a binary data file.
>> what's worng? can somebody tell me where fine documentation?
>
> You should probably be using the 'linuxppc_2_4_devel' tree, see
> http://penguinppc.org/dev/kernel.shtml. Second, 'bzImage' is an alias
I want to make a comment here. On the web page you mention there is no
clear indication on what kernel should be used for PowerCore CPCI-3750
or other embedded platforms especially it does not explain the
difference between the "linuxppc_2_4" and "linuxppc_2_4_devel" tree:
linuxppc_2_4 stable branch
linuxppc_2_4_devel stable branch testing tree
A bit more explanation would be useful.
Wolfgang.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-03-27 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 13:02 Linux on PowerCore CPCI-3750 luca gambazzi
2003-03-27 18:48 ` Tom Rini
2003-03-27 20:13 ` Wolfgang Grandegger [this message]
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=3E835B64.4070103@bluewin.ch \
--to=wolfgang.grandegger@bluewin.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=luca.gambazzi@epfl.ch \
--cc=trini@kernel.crashing.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).