1 |
On Fri, 2019-09-13 at 03:17 +0000, A Schenck wrote: |
2 |
> On 9/10/19 10:24 PM, Michał Górny wrote: |
3 |
> > On Tue, 2019-09-10 at 22:44 +0200, Michał Górny wrote: |
4 |
> > > Hi, everyone. |
5 |
> > > |
6 |
> > > I've recently (finally!) started adding tests to cpuid2cpuflags. Tests |
7 |
> > > are based on mocked syscalls that return arch-specific data read from |
8 |
> > > text files. So far I've got x86 and ppc covered, and now I'd like to |
9 |
> > > add tests for various arm hardware. Since ARM covers a pretty broad |
10 |
> > > range of hardware, I'd use as much data as possible, especially from |
11 |
> > > different ARM generations. |
12 |
> > > |
13 |
> > > If you have an ARM board and would like to help, please: |
14 |
> > > |
15 |
> > > wget https://dev.gentoo.org/~mgorny/dist/cpuid2cpuflags-7-dev.tar.bz2 |
16 |
> > > tar -xf cpuid2cpuflags-7-dev.tar.bz2 |
17 |
> > > cd cpuid2cpuflags-7-dev |
18 |
> > > ./configure |
19 |
> > > make hwcap-dump |
20 |
> > > ./hwcap-dump |
21 |
> > > |
22 |
> > > and send me the output along with 'uname -m'. TIA! |
23 |
> > > |
24 |
> > I'm sorry but sending it this late, I forgot two more important things: |
25 |
> > |
26 |
> > 1. Name of the CPU or the board (i.e. something I can use to name |
27 |
> > the test). |
28 |
> > |
29 |
> > 2. Output of cpuid2cpuflags, preferably verified against cpuinfo. |
30 |
> > |
31 |
> Don't laugh, it actually still works as a NAS and nextcloud server: |
32 |
> |
33 |
> amphisbœna ~/cpuid2cpuflags-7-dev # ./hwcap-dump |
34 |
> uhwcap:0000000000000097 |
35 |
> hwcap2:0000000000000000 |
36 |
> |
37 |
> namphisbœna ~/cpuid2cpuflags-7-dev # uname -m |
38 |
> armv5tel |
39 |
> |
40 |
> amphisbœna ~/cpuid2cpuflags-7-dev # ./cpuid2cpuflags |
41 |
> CPU_FLAGS_ARM: edsp thumb v4 v5 |
42 |
> |
43 |
|
44 |
Thank you! Finally something older than v7 ;-). All old hardware |
45 |
appreciated to improve test coverage. |
46 |
|
47 |
-- |
48 |
Best regards, |
49 |
Michał Górny |