From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] tool chain
Date: Fri, 20 Jan 2006 08:09:25 -0500 [thread overview]
Message-ID: <43D0E105.7070302@smiths-aerospace.com> (raw)
In-Reply-To: <001301c61dba$c508ab00$9e01120a@bilisim.local>
Mustafa ?ay?r wrote:
> hi,
>
> Cold you give me advice? how can setup tool-chain for ppc target. What
> is stable version of necessary parts. My host machine is i386, target is
> ppc MPC7457.
>
> Thanks.
Debugger: BDI2000 (you will find that the overwhelming answer on this list).
Toolchain: <http://www.denx.de/en/Software/WebHome>
<http://www.denx.de/wiki/view/DULG/ELDKAvailability>
* ELDK3.1 if you want to be based on the 2.4 kernel
* ELDK4.0 if you want to be based on the 2.6 kernel
<http://www.denx.de/en/News/PressReleaseELDK40>
Don't send HTML, Wolfgang still hasn't recovered from the last episode.
Since he does all the thankless work of maintaining u-boot and eldk
while we do the fun coding stuff, we don't want to annoy him
unnecessarily, do we? ;-)
gvb
prev parent reply other threads:[~2006-01-20 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 12:12 [U-Boot-Users] tool chain Mustafa Çayır
2006-01-20 13:09 ` Jerry Van Baren [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=43D0E105.7070302@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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