From: James Cloos <cloos@jhcloos.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need ARM/AArch64 test data for cpuid2cpuflags
Date: Thu, 12 Sep 2019 09:13:33 -0400 [thread overview]
Message-ID: <m3ftl13beq.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <d81cfd14e617804383aea4bf2cca80278e1d6980.camel@gentoo.org> ("Michał Górny"'s message of "Tue, 10 Sep 2019 22:44:54 +0200")
On an odroidc1, I get:
# ./hwcap-dump
hwcap:000000000009b0d7
hwcap2:0000000000000000
# uname -m
armv7l
On an original dragonboard, I get:
# ./hwcap-dump
hwcap:0000000000000087
hwcap2:0000000000000000
# uname -m
aarch64
(Both run gentoo.)
The pi3 says:
hwcap:00000000003fb0d6
hwcap2:0000000000000010
armv7l
I have a couple of cheap arm32 (don't recall manuf) which report:
hwcap:00000000000fb8d7
hwcap2:0000000000000000
armv7l
A c.h.i.p. says:
hwcap:000000000008b0d6
hwcap2:0000000000000000
armv7l
All of my other arm boards are offline.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2019-09-12 13:13 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 [this message]
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=m3ftl13beq.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.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