From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2009.08-rc3 is out
Date: Tue, 21 Dec 2010 15:36:16 +0100 [thread overview]
Message-ID: <4D10BB60.9020800@scharsoft.de> (raw)
In-Reply-To: <20090822214116.7BD67833DBD2@gemini.denx.de>
Am 22.08.2009 23:41, schrieb Wolfgang Denk:
> Hi everybody...
>
> v2009.08-rc3 has just been released.
>
> Please help testing, and submit fixes to the remaining problems.
>
Hello,
I have tested the EB+CPUx9K2 Board. It can be compiled with gcc 4.2.2 (ELDK)
and gcc 4.5.1 (buildroot 2010.11).
But it runs only , if I use the newer 4.5.1 toolchain. I think, there are
toolchain issues with relocation
Regards
Jens Scharsig
next prev parent reply other threads:[~2010-12-21 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 21:41 [U-Boot] [STATUS] v2009.08-rc3 is out Wolfgang Denk
2009-08-22 23:08 ` Mike Frysinger
2009-08-23 20:21 ` Wolfgang Denk
2010-12-21 14:36 ` Jens Scharsig [this message]
2010-12-21 14:50 ` Wolfgang Denk
2010-12-21 18:04 ` Jens Scharsig
2010-12-22 9:29 ` Jens Scharsig
2010-12-22 9:37 ` Jens Scharsig
2010-12-22 10:00 ` Reinhard Meyer
2010-12-22 10:50 ` Jens Scharsig
2010-12-22 9:41 ` Jens Scharsig
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=4D10BB60.9020800@scharsoft.de \
--to=js_at_ng@scharsoft.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