From: Nick Howell <nlhowell@gmail.com>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Cc: arm <arm@gentoo.org>
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Wed, 11 Sep 2019 09:42:21 +0300 [thread overview]
Message-ID: <5d78974d83515_61723ae503440529@mercury.mail> (raw)
In-Reply-To: <1ae2785f3891fd9fa3897bfd1ebdc73c330eee43.camel@gentoo.org>
Michał Górny wrote:
> On Tue, 2019-09-10 at 22:44 +0200, Michał Górny wrote:
> > If you have an ARM board and would like to help, please:
> >
> > ./hwcap-dump
> >
> > and send me the output along with 'uname -m'. TIA!
>
> I'm sorry but sending it this late, I forgot two more important things:
>
> 1. Name of the CPU or the board (i.e. something I can use to name
> the test).
>
> 2. Output of cpuid2cpuflags, preferably verified against cpuinfo.
name: rk3288
$ uname -m
armv7l
$ ./hwcap-dump
hwcap:00000000003fb8d7
hwcap2:0000000000000000
$ ./cpuid2cpuflags
CPU_FLAGS_ARM: edsp neon thumb vfp vfpv3 vfpv4 vfp-d32 v4 v5 v6 v7 thumb2
$ grep -m1 Features /proc/cpuinfo
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
$ diff -U0 <(./cpuid2cpuflags | tr ' ' '\n' | sed 1d |sort) <(grep -m1 Features /proc/cpuinfo | tr ' ' '\n' | sed 1d | grep '.' |sort)
--- /dev/fd/63 2019-09-11 09:38:40.710312547 +0300
+++ /dev/fd/62 2019-09-11 09:38:40.710312547 +0300
@@ -1,0 +2,6 @@
+evtstrm
+fastmult
+half
+idiva
+idivt
+lpae
@@ -2,0 +9 @@
+swp
@@ -4,5 +11,2 @@
-thumb2
-v4
-v5
-v6
-v7
+thumbee
+tls
@@ -10 +14 @@
-vfp-d32
+vfpd32
next prev parent reply other threads:[~2019-09-11 6:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 20:44 [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags Michał Górny
2019-09-11 5:24 ` Michał Górny
2019-09-11 6:42 ` Nick Howell [this message]
2019-09-11 6:52 ` Michał Górny
2019-09-12 11:29 ` Rolf Eike Beer
2019-09-12 13:38 ` Michał Górny
2019-09-13 3:17 ` A Schenck
2019-09-13 5:03 ` Michał Górny
2019-09-11 17:09 ` Georgy Yakovlev
2019-09-11 17:33 ` Michał Górny
2019-09-11 18:02 ` Matt Turner
2019-09-11 18:15 ` Michał Górny
2019-09-11 20:19 ` James Le Cuirot
2019-09-11 20:37 ` Michał Górny
2019-09-12 13:13 ` James Cloos
2019-09-12 13:47 ` Michał Górny
2019-09-17 20:56 ` Michał Górny
2019-09-18 12:56 ` Alfredo Tupone
2019-09-25 15:22 ` Guilherme Amadio
2019-09-25 16:03 ` Michał Górny
2019-10-01 11:48 ` Roy Bamford
2019-10-02 15:30 ` Piotr Szymaniak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d78974d83515_61723ae503440529@mercury.mail \
--to=nlhowell@gmail.com \
--cc=arm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox