| 1 |
On Thu, 2019-09-12 at 13:29 +0200, Rolf Eike Beer wrote: |
| 2 |
> Am 2019-09-11 07:24, schrieb Michał Górny: |
| 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. |
| 7 |
> > > Tests |
| 8 |
> > > are based on mocked syscalls that return arch-specific data read from |
| 9 |
> > > text files. So far I've got x86 and ppc covered, and now I'd like to |
| 10 |
> > > add tests for various arm hardware. Since ARM covers a pretty broad |
| 11 |
> > > range of hardware, I'd use as much data as possible, especially from |
| 12 |
> > > different ARM generations. |
| 13 |
> > > |
| 14 |
> > > If you have an ARM board and would like to help, please: |
| 15 |
> > > |
| 16 |
> > > wget https://dev.gentoo.org/~mgorny/dist/cpuid2cpuflags-7-dev.tar.bz2 |
| 17 |
> > > tar -xf cpuid2cpuflags-7-dev.tar.bz2 |
| 18 |
> > > cd cpuid2cpuflags-7-dev |
| 19 |
> > > ./configure |
| 20 |
> > > make hwcap-dump |
| 21 |
> > > ./hwcap-dump |
| 22 |
> > > |
| 23 |
> > > and send me the output along with 'uname -m'. TIA! |
| 24 |
> > > |
| 25 |
> > |
| 26 |
> > I'm sorry but sending it this late, I forgot two more important things: |
| 27 |
> > |
| 28 |
> > 1. Name of the CPU or the board (i.e. something I can use to name |
| 29 |
> > the test). |
| 30 |
> > |
| 31 |
> > 2. Output of cpuid2cpuflags, preferably verified against cpuinfo. |
| 32 |
> |
| 33 |
> Wandboard: |
| 34 |
> |
| 35 |
> # uname -m |
| 36 |
> armv7l |
| 37 |
> # hwcap-dump |
| 38 |
> hwcap:000000000008b8d6 |
| 39 |
> hwcap2:0000000000000000 |
| 40 |
> |
| 41 |
|
| 42 |
Thanks. This is identical to Beaglebone, so I'm gonna skip it. |
| 43 |
|
| 44 |
-- |
| 45 |
Best regards, |
| 46 |
Michał Górny |
Archives