From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v16 00/10] arm64 patch
Date: Thu, 9 Jan 2014 17:01:32 +0100 [thread overview]
Message-ID: <20140109170132.5fb8d535@lilith> (raw)
In-Reply-To: <1386992858-44800-1-git-send-email-fenghua@phytium.com.cn>
Hi fenghua at phytium.com.cn,
On Sat, 14 Dec 2013 11:47:28 +0800, fenghua at phytium.com.cn wrote:
> From: David Feng <fenghua@phytium.com.cn>
>
> Changes for v16:
> - make the patches work with latest recently u-boot.
> add rela relocation type to OBJCFLAGS definition
> at arm/config.mk.
The series applies well and builds armv8 targets well if I set the
CROSS_COMPILE prefix to a 64-bit toolchain. However, if I use a 32-bit
toolchain prefix,
1) it still tries to build armv8 target, and fails understandably;
2) it causes the following boards to fail building:
trats2 snow smdk5250 vexpress_aemv8a smdkv310 origen s5pc210_universal
trats s5p_goni smdkc100 smdk5420 arndale
All with the same error, starting with:
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h:45:1:
error: unknown type name '__le64'
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h: In
function '__cpu_to_le64p':
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h:47:18:
error: '__le64' undeclared (first use in this function)
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h:47:18:
note: each undeclared identifier is reported only once for each function it appears in
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h: At
top level:
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h:49:1:
error: unknown type name '__le64'
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h:53:1:
error: unknown type name '__le32'
/home/albert/src/u-boot-arm/include/linux/byteorder/little_endian.h: In
function '__cpu_to_le32p':
Etc.
Can you look into it on your side and determine what causes this? I
don't necessarily need a v16 series; a bugfix patch is ok.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-01-09 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 3:47 [U-Boot] [PATCH v16 00/10] arm64 patch fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 01/10] fdt_support: 64bit initrd start address support fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 02/10] cmd_pxe: remove compiling warnings fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 03/10] add weak entry definition fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 04/10] arm64: Add tool to statically apply RELA relocations fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 05/10] arm64: Turn u-boot.bin back into an ELF file after relocate-rela fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 06/10] arm64: Make checkarmreloc accept arm64 relocations fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 07/10] arm64: core support fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 08/10] arm64: generic board support fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 09/10] arm64: board support of vexpress_aemv8a fenghua at phytium.com.cn
2013-12-14 3:47 ` [U-Boot] [PATCH v16 10/10] arm64: MAKEALL, filter armv8 boards from LIST_arm fenghua at phytium.com.cn
2013-12-14 5:09 ` [U-Boot] [PATCH v16 04/10] arm64: Add tool to statically apply RELA relocations Jagan Teki
2013-12-16 18:12 ` Scott Wood
2013-12-14 5:05 ` [U-Boot] [PATCH v16 02/10] cmd_pxe: remove compiling warnings Jagan Teki
2013-12-19 14:27 ` FengHua
2014-01-09 16:01 ` Albert ARIBAUD [this message]
2014-01-10 1:58 ` [U-Boot] [PATCH v16 00/10] arm64 patch TigerLiu at viatech.com.cn
2014-01-10 9:14 ` Albert ARIBAUD
2014-01-10 9:17 ` Albert ARIBAUD
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=20140109170132.5fb8d535@lilith \
--to=albert.u.boot@aribaud.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.