ARMv4 vs ARMv6
k.kooi at student.utwente.nl
Thu Oct 16 15:31:41 CEST 2008
Op 16 okt 2008, om 15:02 heeft Andy Green het volgende geschreven:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Somebody in the thread at some point said:
> | I don't know the details of ARMv4/v6/VFP interaction, but I
> believe it is
> | all the same ABI (EABI), and you should very well be able to link
> a ARMv6
> | application against an ARMv4 library.
> It comes down to the same thing though in packaging. If someone
> bothered to build an ARMv6-specific mplayer binary for example, so
> can squeeze out 1 more fps, they are going to build it to "require"
> the ARMv6 libs mplayer likes, eg ffmpeg and aac stuff.
It wouldn't 'require' armv6 libs, it would still work fine if you
install the armv6 mplayer with only armv4t libs in the rootfs. And
FWIW, I expect mplayer to run approx. twice as fast when compiled with
armv6 since ffmpeg has seen a lot of optimization for armv6 (and
And more importantly: mplayer has an internal copy of ffmpeg, so your
example doesn't fly.
> You might have
> something else installed on the same box that required the v4 ones
> so the /usr/lib and /usr/lib64 type thing is needed for same library /
> different arch coexistence on one system. It is like the i386 /
> multiarch situation.
As Harald, Graeme and I said before: no, it's not like that
> Like I said I am sure all of this can be handled, but I am equally
> it isn't going to "just work" without care taken in the toolchain and
> distro ends, and it's the kind of thing that needs to be right from
It already "Just Works(TM)" in OE and Angstrom, so no problem there.
There *might* be problems when people want to build *packages* only
using the toolchain, but those people get what they asked for.
> Anyway it sounds like the feel is that we do not ignore it and stick
> with ARMv4 all over, so at least we know what we are headed towards
> and can start dealing with it.
> - -Andy
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.openmoko.org/pipermail/devel/attachments/20081016/d44f76eb/attachment.pgp
More information about the devel