Dear Thierry Reding,
In message 1321524246-5187-2-git-send-email-thierry.red...@avionic-design.de
you wrote:
The AVP on Tegra2 doesn't boot properly when U-Boot is linked against
the GCC provided libgcc. To work around this, always build and link
against a private libgcc for Tegra2-based
On 01/05/2012 08:50 AM, Wolfgang Denk wrote:
Dear Thierry Reding,
In message
1321524246-5187-2-git-send-email-thierry.red...@avionic-design.de you wrote:
The AVP on Tegra2 doesn't boot properly when U-Boot is linked against
the GCC provided libgcc. To work around this, always build and
Hi Stephen,
On Thu, Jan 5, 2012 at 8:53 AM, Stephen Warren swar...@nvidia.com wrote:
On 01/05/2012 08:50 AM, Wolfgang Denk wrote:
Dear Thierry Reding,
In message
1321524246-5187-2-git-send-email-thierry.red...@avionic-design.de you
wrote:
The AVP on Tegra2 doesn't boot properly when
Simon,
-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Thursday, January 05, 2012 10:07 AM
To: Stephen Warren
Cc: Wolfgang Denk; Thierry Reding; u-boot@lists.denx.de; Tom Warren
Subject: Re: [U-Boot] [PATCH 1/2] tegra2: Always build
Dear Stephen Warren,
In message 4f05d596.6030...@nvidia.com you wrote:
I will accept this only temporarily. Why don't you use a working tool
chain instead, or fix the one you are using?
I believe the issue isn't that the toolchain is broken, but due to the
mix of multiple CPU types on
Dear Simon Glass,
In message capnjgz2wcqf2tpwwfudkg7y_xdeyhbfrenqxxrjg6eu7yj9...@mail.gmail.com
you wrote:
The libraries included in the toolchain are built for the ARMv7 CPUs,
and hence fail to operate correctly when used by the portion of U-Boot
which runs on the ARMv4 CPU, presumably
On 01/05/2012 12:16 PM, Wolfgang Denk wrote:
In message 4f05d596.6030...@nvidia.com you wrote:
...
The libraries included in the toolchain are built for the ARMv7 CPUs,
SO this is not the right tool chain for the job. Ecactly what I said.
and hence fail to operate correctly when used by
Dear Stephen Warren,
In message 4f05fcbd.2040...@nvidia.com you wrote:
No, this is NOT a solution, it is a workaround for an inappropriate
toolchain. If you want to build code for an armv4t system, you must
use a tool chain that supports it.
But we don't want to generate code for ARMv4
Hi,
On Thu, Jan 5, 2012 at 12:17 PM, Wolfgang Denk w...@denx.de wrote:
Dear Stephen Warren,
In message 4f05fcbd.2040...@nvidia.com you wrote:
No, this is NOT a solution, it is a workaround for an inappropriate
toolchain. If you want to build code for an armv4t system, you must
use a
On 01/05/2012 01:42 PM, Simon Glass wrote:
Hi,
On Thu, Jan 5, 2012 at 12:17 PM, Wolfgang Denk w...@denx.de wrote:
Dear Stephen Warren,
In message 4f05fcbd.2040...@nvidia.com you wrote:
No, this is NOT a solution, it is a workaround for an inappropriate
toolchain. If you want to build
Dear Stephen,
In message 4f060dd1.9050...@nvidia.com you wrote:
It might be possible to specify ARMv4T on the link flags and have it
pick up the v4T library, even if nearly everything else is ARMv7?
I don't think we use any multilib toolchains, so I don't think that's
possible.
I don't
The AVP on Tegra2 doesn't boot properly when U-Boot is linked against
the GCC provided libgcc. To work around this, always build and link
against a private libgcc for Tegra2-based boards.
Signed-off-by: Thierry Reding thierry.red...@avionic-design.de
---
arch/arm/cpu/armv7/tegra2/config.mk |
On Thu, Nov 17, 2011 at 2:04 AM, Thierry Reding
thierry.red...@avionic-design.de wrote:
The AVP on Tegra2 doesn't boot properly when U-Boot is linked against
the GCC provided libgcc. To work around this, always build and link
against a private libgcc for Tegra2-based boards.
Signed-off-by:
13 matches
Mail list logo
