From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Wed, 11 Sep 2019 21:19:22 +0100 [thread overview]
Message-ID: <20190911211922.3abeca0d@symphony.aura-online.co.uk> (raw)
In-Reply-To: <d81cfd14e617804383aea4bf2cca80278e1d6980.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On Tue, 10 Sep 2019 22:44:54 +0200
Michał Górny <mgorny@gentoo.org> 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:
From my CompuLab Utilite Pro:
$ ./hwcap-dump
hwcap:000000000008b0d6
hwcap2:0000000000000000
$ ./cpuid2cpuflags
CPU_FLAGS_ARM: edsp neon thumb vfp vfpv3 vfp-d32 v4 v5 v6 v7 thumb2
$ uname -a
Linux utilite 5.2.7-00007-g4559111aee7b #100 SMP PREEMPT Wed Aug 7 23:24:36 BST 2019 armv7l ARMv7 Processor rev 10 (v7l) Freescale i.MX6 Quad/DualLite (Device Tree) GNU/Linux
$ cat /proc/cpuinfo
...
processor : 3
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 6.00
Features : half thumb fastmult vfp edsp 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
--
James Le Cuirot (chewi)
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-11 20:19 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
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 [this message]
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=20190911211922.3abeca0d@symphony.aura-online.co.uk \
--to=chewi@gentoo.org \
--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