| commit | 58eb53083ccac82bc9c8e4b5f0800dcc47d22927 | |
| author | Michael Walle <michael@walle.cc> | |
| Wed, 21 Sep 2016 09:57:05 +0000 (21 11:57 +0200) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Fri, 23 Sep 2016 02:39:07 +0000 (23 12:39 +1000) | ||
| tree | 5c71353d54943732c8be8c8b2038b81c0e886f58 | treesnapshot (tar.gz zip) |
| parent | 0d594f5565837fe2886a8aa307ef8abb65eab8f7 | commitdiff |
linux-user: ppc64: fix ARCH_206 bit in AT_HWCAP
Only the POWER[789] CPUs should have the ARCH_206 bit set. This is what the
linux kernel does. I guess this was also the intention of commit 0e019746.
We have to make sure all *206 bits are set.
Before this patch, the flags check in the GET_FEATURES2 macro returned true
if _any_ bit was set. This worked well as long as there was only one bit
set in the 'flag' parameter. But as explained before, we have to make sure
all bits in the 'flag' parameter are set.
Signed-off-by: Michael Walle <michael@walle.cc>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Only the POWER[789] CPUs should have the ARCH_206 bit set. This is what the
linux kernel does. I guess this was also the intention of commit 0e019746.
We have to make sure all *206 bits are set.
Before this patch, the flags check in the GET_FEATURES2 macro returned true
if _any_ bit was set. This worked well as long as there was only one bit
set in the 'flag' parameter. But as explained before, we have to make sure
all bits in the 'flag' parameter are set.
Signed-off-by: Michael Walle <michael@walle.cc>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
| linux-user/elfload.c | diffblobblamehistory |