public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: A Schenck <lane_andrew@hotmail.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Fri, 13 Sep 2019 03:17:43 +0000	[thread overview]
Message-ID: <SN6PR17MB2110238A436BB3AB1E0025999DB30@SN6PR17MB2110.namprd17.prod.outlook.com> (raw)
In-Reply-To: <1ae2785f3891fd9fa3897bfd1ebdc73c330eee43.camel@gentoo.org>

On 9/10/19 10:24 PM, 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!
>>
> 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.
>
Don't laugh, it actually still works as a NAS and nextcloud server:

amphisbœna ~/cpuid2cpuflags-7-dev # ./hwcap-dump
uhwcap:0000000000000097
hwcap2:0000000000000000

namphisbœna ~/cpuid2cpuflags-7-dev # uname -m
armv5tel

amphisbœna ~/cpuid2cpuflags-7-dev # ./cpuid2cpuflags
CPU_FLAGS_ARM: edsp thumb v4 v5

amphisbœna ~/cpuid2cpuflags-7-dev # dog /proc/cpuinfo
processor       : 0
model name      : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS        : 400.00
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

Hardware        : Marvell Kirkwood (Flattened Device Tree)
Revision        : 0000
Serial          : 0000000000000000

amphisbœna ~/cpuid2cpuflags-7-dev # dog /proc/device-tree/model
Globalscale Technologies Dreamplug



  parent reply	other threads:[~2019-09-13  3:17 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 [this message]
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=SN6PR17MB2110238A436BB3AB1E0025999DB30@SN6PR17MB2110.namprd17.prod.outlook.com \
    --to=lane_andrew@hotmail.com \
    --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