public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] ARMV7: Fixing Vexpress build errors and warnings
Date: Mon, 29 Nov 2010 19:56:59 +0100	[thread overview]
Message-ID: <4CF3F77B.9080505@googlemail.com> (raw)
In-Reply-To: <4CF3ED5F.50703@free.fr>

On 29.11.2010 19:13, Albert ARIBAUD wrote:
> Le 03/11/2010 00:25, matt.waddel at linaro.org a ?crit :
>> From: Matt Waddel<matt.waddel@linaro.org>
>>
>> These patches fix several build errors and warnings. A successful build for
>> this platform depends on Steve Sakoman's "ARMV7: Fix build for non-OMAP3
>> boards" patch.
>>
>> Matt Waddel (2):
>>     ARMV7: Vexpress build errors
>>     ARMV7: Vexpress compile warnings
>>
>>    arch/arm/include/asm/arch-armv7/sys_proto.h |   29 ++++++++++++
>>    board/armltd/vexpress/ca9x4_ct_vxp.c        |    9 +++-
>>    board/armltd/vexpress/config.mk             |    3 +-
>>    board/armltd/vexpress/u-boot.lds            |   65 ---------------------------
>>    4 files changed, 36 insertions(+), 70 deletions(-)
>>    create mode 100644 arch/arm/include/asm/arch-armv7/sys_proto.h
>>    delete mode 100644 board/armltd/vexpress/u-boot.lds
>
> Wofgang, maybe I can take over u-boot-arm now and start by applying
> these two patches (and let you pull u-boot-arm later this week)?

With recent master, besides the two patches above, I additionally need 
something like below to get ca9x4_ct_vxp build:

ARMV7: Vexpress: Fix build error

Fix ca9x4_ct_vxp build error

Configuring for ca9x4_ct_vxp board...
board/armltd/vexpress/libvexpress.o: In function `udelay':
u-boot.git/board/armltd/vexpress/ca9x4_ct_vxp.c:161: multiple 
definition of `udelay'
lib/libgeneric.o:u-boot.git/lib/time.c:34: first defined here 

lib/libgeneric.o: In function `udelay': 

zlib.c:(.text+0x1ee8): undefined reference to `__udelay'

Signed-of-by: Dirk Behme <dirk.behme@googlemail.com>

---
  board/armltd/vexpress/ca9x4_ct_vxp.c |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

Index: u-boot.git/board/armltd/vexpress/ca9x4_ct_vxp.c
===================================================================
--- u-boot.git.orig/board/armltd/vexpress/ca9x4_ct_vxp.c
+++ u-boot.git/board/armltd/vexpress/ca9x4_ct_vxp.c
@@ -157,7 +157,7 @@ void reset_cpu(ulong addr)
   * Delay x useconds AND perserve advance timstamp value
   *     assumes timer is ticking at 1 msec
   */
-void udelay(ulong usec)
+void __udelay(ulong usec)
  {
  	ulong tmo, tmp;

  reply	other threads:[~2010-11-29 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 23:25 [U-Boot] [PATCH 0/2] ARMV7: Fixing Vexpress build errors and warnings matt.waddel at linaro.org
2010-11-02 23:25 ` [U-Boot] [PATCH 1/2] ARMV7: Vexpress build errors matt.waddel at linaro.org
2010-12-02 19:43   ` [U-Boot] [PATCH v2 1/2] " matt.waddel at linaro.org
2010-12-08 22:43     ` Wolfgang Denk
2010-11-02 23:25 ` [U-Boot] [PATCH 2/2] ARMV7: Vexpress compile warnings matt.waddel at linaro.org
2010-12-08 22:45   ` Wolfgang Denk
2010-11-17 21:36 ` [U-Boot] [PATCH 0/2] ARMV7: Fixing Vexpress build errors and warnings Loïc Minier
2010-11-29 18:13 ` Albert ARIBAUD
2010-11-29 18:56   ` Dirk Behme [this message]
2010-12-08 22:47     ` Wolfgang Denk

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=4CF3F77B.9080505@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --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