From: Rolf Eike Beer <eike@sf-mail.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Thu, 12 Sep 2019 13:29:06 +0200 [thread overview]
Message-ID: <19127c489c842ed89deff09825b32598@sf-mail.de> (raw)
In-Reply-To: <1ae2785f3891fd9fa3897bfd1ebdc73c330eee43.camel@gentoo.org>
Am 2019-09-11 07:24, schrieb Michał Górny:
> On Tue, 2019-09-10 at 22:44 +0200, Michał Górny wrote:
>> Hi, everyone.
>>
>> I've recently (finally!) started adding tests to cpuid2cpuflags.
>> Tests
>> are based on mocked syscalls that return arch-specific data read from
>> text files. So far I've got x86 and ppc covered, and now I'd like to
>> add tests for various arm hardware. Since ARM covers a pretty broad
>> range of hardware, I'd use as much data as possible, especially from
>> different ARM generations.
>>
>> If you have an ARM board and would like to help, please:
>>
>> wget https://dev.gentoo.org/~mgorny/dist/cpuid2cpuflags-7-dev.tar.bz2
>> tar -xf cpuid2cpuflags-7-dev.tar.bz2
>> cd cpuid2cpuflags-7-dev
>> ./configure
>> make hwcap-dump
>> ./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.
Wandboard:
# uname -m
armv7l
# hwcap-dump
hwcap:000000000008b8d6
hwcap2:0000000000000000
# ./cpuid2cpuflags
CPU_FLAGS_ARM: edsp neon thumb vfp vfpv3 vfp-d32 v4 v5 v6 v7 thumb2
# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 7.54
Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls
vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : Freescale i.MX6 Quad/DualLite (Device Tree)
Revision : 0000
Serial : 0000000000000000
Eike
next prev parent reply other threads:[~2019-09-12 11:30 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
2019-09-11 6:52 ` Michał Górny
2019-09-12 11:29 ` Rolf Eike Beer [this message]
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=19127c489c842ed89deff09825b32598@sf-mail.de \
--to=eike@sf-mail.de \
--cc=gentoo-dev@lists.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