On Mon, Jan 05, 2015 at 12:24:13PM +0000, B.R. Oake wrote:
On 05/01/15 10:51, Hans de Goede wrote:
Ah, ok, thanks for figuring that out, so this only happens to people following my sunxi-wip branch, because that commit is not upstream yet.
So I guess I will need to fix this somehow without using 64 bit math, any suggestions?
EDID_DETAILED_TIMING_PIXEL_CLOCK() always returns a uint32 that is 10,000 times a uint16, so one way of avoiding 64-bit arithmetic would be to cancel out the 10,000 before the division:
Good idea!
[snip]
I still wonder though whether a nicer way would be for the configs to be refactored so that -msoft-float was not set on platforms where it wasn't appropriate.
We've gone over this before (so there's discussions in the archive) but in sum, no, we don't want to get into doing floating point.