public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alfredo Tupone <tupone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Wed, 18 Sep 2019 14:56:49 +0200	[thread overview]
Message-ID: <20190918125649.GA31585@tupone.it> (raw)
In-Reply-To: <ae3b100adaedbc2ed02bff1d4392175460276430.camel@gentoo.org>

On 22:56 Tue 17 Sep     , Michał Górny wrote:
> 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!
> > 
> 
> Thanks for all the data so far.  I've released v8 with the lot of ARM
> tests just now.
> 
> If someone's got older hardware (<ARMv7), then I'd really use such
> results.  After all, we technically do support ARMv4.
> 
> -- 
> Best regards,
> Michał Górny
> 
Something from my RaspberryPI 1B+

Raspberry Pi 1 Model B+
./hwcap-dump
hwcap:00000000000081d6 hwcap2:0000000000000000
/proc/cpuinfo
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 697.95
Features        : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 0010
Serial          : 00000000e598822e
./cpuid2cpuflags
CPU_FLAGS_ARM: edsp thumb vfp v4 v5 v6
uname -m
armv6l

Regards


  reply	other threads:[~2019-09-18 12:56 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
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 [this message]
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=20190918125649.GA31585@tupone.it \
    --to=tupone@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