public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: B.R. Oake <broake@openmailbox.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cannot compile arm u-boot with hardfloat toolchain
Date: Mon, 05 Jan 2015 10:46:50 +0000	[thread overview]
Message-ID: <54AA6B9A.1070204@openmailbox.org> (raw)
In-Reply-To: <20150105012857.GE10826@bill-the-cat>

On 05/01/15 01:28, Tom Rini wrote:
> On Sun, Jan 04, 2015 at 11:23:29PM +0100, Michal Suchanek wrote:
>> when using a hardfloat toolchain linking u-boot fails.
> 
> What version of U-Boot are you building?  There's a few rc releases that
> fail with hardfp-only because a few things leaked in with 64bit math.

Hi Tom,

I also encountered this problem
( http://lists.denx.de/pipermail/u-boot/2015-January/200123.html )
and found it was indeed when 64-bit maths operations were included.
To be exact, it was this division of a long long in
drivers/video/videomodes.c:

     mode->pixclock = 1000000000000LL / EDID_DETAILED_TIMING_PIXEL_CLOCK(*t);

which was part of this commit in Hans' sunxi video series:

0cd5efe videomodes: Add video_edid_dtd_to_ctfb_res_modes helper function

and which was linked into the u-boot binary in a later commit:

e7872f3 sunxi: video: Use video-mode/-timing from videomodes
diff --git a/drivers/video/Makefile b/drivers/video/Makefile
[...]
-obj-$(CONFIG_VIDEO_SUNXI) += sunxi_display.o
+obj-$(CONFIG_VIDEO_SUNXI) += sunxi_display.o videomodes.o

Thanks,
B.R. Oake.

  parent reply	other threads:[~2015-01-05 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 22:23 [U-Boot] Cannot compile arm u-boot with hardfloat toolchain Michal Suchanek
2015-01-05  1:28 ` Tom Rini
2015-01-05  9:46   ` Michal Suchanek
2015-01-05 10:46   ` B.R. Oake [this message]
2015-01-05 10:51     ` Hans de Goede
2015-01-05 12:08       ` Michael Trimarchi
2015-01-05 12:24       ` B.R. Oake
2015-01-05 13:37         ` Tom Rini
2015-01-05 15:30           ` B.R. Oake
2015-01-05 14:58         ` Hans de Goede

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=54AA6B9A.1070204@openmailbox.org \
    --to=broake@openmailbox.org \
    --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