Le 19/12/2017 à 21:16, Michael Weiser a écrit : > As we now have a linux-user aarch64_be target, we can add it to the list > of supported targets in qemu-binfmt-conf.sh > > Signed-off-by: Michael Weiser <michael.wei...@gmx.de> > --- > scripts/qemu-binfmt-conf.sh | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/scripts/qemu-binfmt-conf.sh b/scripts/qemu-binfmt-conf.sh > index 8afc3eb5bb..d69953525c 100755 > --- a/scripts/qemu-binfmt-conf.sh > +++ b/scripts/qemu-binfmt-conf.sh > @@ -4,7 +4,7 @@ > > qemu_target_list="i386 i486 alpha arm sparc32plus ppc ppc64 ppc64le m68k \ > mips mipsel mipsn32 mipsn32el mips64 mips64el \ > -sh4 sh4eb s390x aarch64 hppa" > +sh4 sh4eb s390x aarch64 aarch64_be hppa" > > > i386_magic='\x7fELF\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x03\x00' > > i386_mask='\xff\xff\xff\xff\xff\xfe\xfe\xff\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff' > @@ -92,6 +92,10 @@ > aarch64_magic='\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x > > aarch64_mask='\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff' > aarch64_family=arm > > +aarch64_be_magic='\x7fELF\x02\x02\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7' > +aarch64_be_mask='\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff' > +aarch64_be_family=arm
You need a different family, something like "armbe", to let qemu_set_binfmts() registers aarch64_be on aarch64 and vice-versa. The principle is binaries of a given family can be executed natively on the host of the same family, so we don't want to register a binfmt handler. Is that the case between aarch64 and arch64_be? Thanks, Laurent
