From: Dirk Behme <dirk.behme@googlemail.com>
To: adapa.ajith@wipro.com
Cc: linux-omap@vger.kernel.org, linux-omap-open-source@linux.omap.com
Subject: Re: Regarding Best Combination for OMAP 2430
Date: Thu, 27 Dec 2007 08:37:15 +0100 [thread overview]
Message-ID: <4773562B.1050402@googlemail.com> (raw)
In-Reply-To: <998B37C19BFDB549AA703C78A86EAA19DC53CF@blr-m1-msg.wipro.com>
adapa.ajith@wipro.com wrote:
> I like to have the best working combination of gcc, binutils, glibc to
> make a cross toolchain for OMAP2430 &
> Kernel version working perfectly with the newly created cross toolchain.
>
> Any links to get the information??
Try CodeSourcery toolchain:
http://www.codesourcery.com/gnu_toolchains/arm
Cheers
Dirk
Btw: Please switch to new OMAP list [1]
http://vger.kernel.org/vger-lists.html#linux-omap
and don't use
linux-omap-open-source@linux.omap.com
any more.
[1] http://marc.info/?l=linux-omap&m=119776551227008&w=3
prev parent reply other threads:[~2007-12-27 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 7:25 Regarding Best Combination for OMAP 2430 adapa.ajith
2007-12-27 7:37 ` Dirk Behme [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=4773562B.1050402@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=adapa.ajith@wipro.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@vger.kernel.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