ARMv4 vs ARMv6
k.kooi at student.utwente.nl
Thu Oct 16 17:03:42 CEST 2008
Op 16 okt 2008, om 16:46 heeft Andy Green het volgende geschreven:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Somebody in the thread at some point said:
> |> Can you spell it out for this idiot WHY it isn't like that? It's
> |> like that because we can't handle parallel install of same lib of
> |> different arch? Or we can handle it fine already? How? Just
> |> me I am wrong and OE is perfect is not really advancing my or
> |> else's understanding of the situation.
> | If I'm understanding the explanations correctly it's analogous to
> | i386, i586 and i686 packages, not to x86 and x86_64 packages.
> | installation isn't needed, and opkg will stop people installing
> | packages on armv4 systems.
> Thanks... still... what actually happens then if you have packages
> requires for v4 libs and another that has requires for v6 of the same
As I said before: It wouldn't 'require' armv6 libs, it would still
work fine if you install the armv6 mplayer with only armv4t libs in
The linker doesn't care about instruction set, it only cares about
ABI, which is this case is the same.
build armv6 rootfs with mplayer
build armv4t rootfs with mplayer
copy over armv6 mplayer binary (no libs) to armv4t rootfs
use rootfs on armv6 device -> mplayer works
It also works with opkg, since the Depends: field only lists name and
version, not arch, since arch is under control of /etc/opkg/arch.conf.
For advanced uses look at what mamona is doing with their 'noemu'
-------------- 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/2a92a2a6/attachment.pgp
More information about the devel