Re: ARMv4 vs ARMv6

[Koen Kooi]

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:


| application against an ARMv4 library.

It comes down to the same thing though in packaging.  If someone

the ARMv6 libs mplayer likes, eg ffmpeg and aac stuff.

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

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 armv6t2). And more importantly: mplayer has an internal copy of ffmpeg, so your example doesn't fly.

 You might have

so the /usr/lib and /usr/lib64 type thing is needed for same library /

multiarch situation.

something else installed on the same box that required the v4 ones too, different arch coexistence on one system. It is like the i386 / x86_64

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 sure

it isn't going to "just work" without care taken in the toolchain and

start.

distro ends, and it's the kind of thing that needs to be right from the

using the toolchain, but those people get what they asked for.

It already "Just Works(TM)" in OE and Angstrom, so no problem there. There *might* be problems when people want to build *packages* only

Anyway it sounds like the feel is that we do not ignore it and stick

and can start dealing with it.

with ARMv4 all over, so at least we know what we are headed towards now

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

PGP.sig
Description: This is a digitally signed message part

_______________________________________________
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel