From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Valentin Longchamp <valentin.longchamp@epfl.ch>
Cc: "linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>,
Dan Williams <dan.j.williams@intel.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Fri, 23 Jan 2009 13:25:01 +0000 [thread overview]
Message-ID: <20090123132501.GJ26184@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4979C472.10707@epfl.ch>
On Fri, Jan 23, 2009 at 02:21:54PM +0100, Valentin Longchamp wrote:
> OK this may be a problem: I use the toolchain that is built by
> OpeneEmbedded. I could give a try to another one. Where can I download
> the ones you use Guennadi or Russel ?
I build my own, direct from ftp.gnu.org. For non-EABI stuff, I use
binutils 2.18 and gcc 3.4.3. For EABI or ARMv7 stuff, I _have_ gcc
4.3.2 but I really don't trust or like it; I try to use gcc 3.4.3
where possible.
I used gcc 4.2.2 for EABI prior to needing ARMv7 support.
And yes, I do have to tweak things a bit to get gcc to build without
glibc - since all I'm interested in is a cross compiler for building
kernels.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
next prev parent reply other threads:[~2009-01-23 13:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 18:04 [PATCH 0/4 v8] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2009-01-08 18:04 ` [PATCH 1/4 v8] dmaengine: add async_tx_clear_ack() macro Guennadi Liakhovetski
2009-01-08 18:04 ` [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2009-01-16 9:59 ` Sascha Hauer
2009-01-22 18:51 ` Valentin Longchamp
2009-01-22 19:04 ` Guennadi Liakhovetski
2009-01-22 19:48 ` Valentin Longchamp
2009-01-22 20:27 ` Guennadi Liakhovetski
2009-01-23 9:30 ` Valentin Longchamp
2009-01-23 9:46 ` Guennadi Liakhovetski
2009-01-23 11:22 ` Valentin Longchamp
2009-01-23 11:34 ` Russell King - ARM Linux
2009-01-23 12:13 ` Guennadi Liakhovetski
2009-01-23 13:01 ` Valentin Longchamp
2009-01-23 13:08 ` Russell King - ARM Linux
2009-01-23 13:12 ` Guennadi Liakhovetski
2009-01-23 13:18 ` Russell King - ARM Linux
2009-01-23 13:21 ` Valentin Longchamp
2009-01-23 13:25 ` Russell King - ARM Linux [this message]
2009-01-23 13:27 ` Guennadi Liakhovetski
2009-01-23 13:54 ` Holger Schurig
2009-01-23 20:55 ` Robert Schwebel
2009-01-23 13:22 ` Guennadi Liakhovetski
2009-01-23 13:26 ` Russell King - ARM Linux
2009-01-23 14:51 ` Valentin Longchamp
2009-01-23 15:09 ` Valentin Longchamp
2009-01-08 18:05 ` [PATCH 3/4 v8] i.MX31: framebuffer driver Guennadi Liakhovetski
2009-01-16 10:00 ` Sascha Hauer
2009-01-08 18:05 ` [PATCH 4/4 v8] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
2009-01-09 8:17 ` [PATCH 0/4 v8] i.MX31: dmaengine " Sascha Hauer
2009-01-09 8:27 ` Guennadi Liakhovetski
2009-01-09 10:09 ` Sascha Hauer
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=20090123132501.GJ26184@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=valentin.longchamp@epfl.ch \
/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).