From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot and ELDK
Date: Thu, 18 Sep 2008 09:01:27 +0200 [thread overview]
Message-ID: <20080918070128.04B78248C6@gemini.denx.de> (raw)
In-Reply-To: <40a670230809171723s5928d870n9c3b2ba4dd53ad91@mail.gmail.com>
Dear "Roman Mashak",
In message <40a670230809171723s5928d870n9c3b2ba4dd53ad91@mail.gmail.com> you wrote:
>
> One more question to clarify my doubts: it's valid to use ELDK
> toolchain for both building bootloader and linux kernel? I ever
That's the whole intention of the ELDK - one single tool chain for
boot loader, Linux kernel and application code. Anything else is a
nightmare and simply not acceptable for production use.
> encountered cases where two distinct toolchains were used to compile
> u-boot and kernel, target was ARM9. Does it make sense, and what might
> be the reasons for that?
There are several subtly broken tool chains out that that can be used
for one thing but not for another. They are just that: broken.
I don't want to suggest that the ELDK has no problems, but at least
this is not one of them.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Die ganzen Zahlen hat der liebe Gott geschaffen, alles andere ist
Menschenwerk... Leopold Kronecker
prev parent reply other threads:[~2008-09-18 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 6:59 [U-Boot] U-Boot and ELDK Roman Mashak
2008-09-12 9:00 ` Wolfgang Denk
2008-09-12 12:15 ` Jerry Van Baren
[not found] ` <40a670230809120341v59adb42q4ac5d2a4bca631ff@mail.gmail.com>
[not found] ` <20080912105709.AE0952491D@gemini.denx.de>
2008-09-18 0:23 ` Roman Mashak
2008-09-18 7:01 ` Wolfgang Denk [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=20080918070128.04B78248C6@gemini.denx.de \
--to=wd@denx.de \
--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