ARMv4 vs ARMv6

[Andy Green]

-----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 they
can squeeze out 1 more fps, they are going to build it to "require" all
the ARMv6 libs mplayer likes, eg ffmpeg and aac stuff.  You might have
something else installed on the same box that required the v4 ones too,
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 / x86_64
multiarch situation.

Like I said I am sure all of this can be handled, but I am equally sure
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 the
start.

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 now
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

iEYEARECAAYFAkj3Ov8ACgkQOjLpvpq7dMosQACfRa+eAxEzKY3ITkFnIxIY3smr
EXsAnipmg71N5Du6473GJll2Mwo9xLVf
=II78
-----END PGP SIGNATURE-----