(In reply to Randell Jesup [:jesup] (needinfo me) from comment #16) > > I don't have Moto G5 now. but, As chip, it supports AES, but some vendor may disable it on aarch32 mode of Linux kernel. When browsing file:///proc/cpuinfo can show current support. (If you want to know aarch32's support, you have to use 32-bit program) > > bogomips: 38.0 half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32 Hmm, I guess that Moto G5's kernel doesn't return 0 with AT_HWCAP2. By bug 1562611, I will add telemetry for it and I will change CPU detection of arm.h to use cpu-features on Android.
Bug 1556022 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Randell Jesup [:jesup] (needinfo me) from comment #16) > > I don't have Moto G5 now. but, As chip, it supports AES, but some vendor may disable it on aarch32 mode of Linux kernel. When browsing file:///proc/cpuinfo can show current support. (If you want to know aarch32's support, you have to use 32-bit program) > > bogomips: 38.0 half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32 Hmm, I guess that Moto G5's kernel doesn't return valid feature with AT_HWCAP2. By bug 1562611, I will add telemetry for it and I will change CPU detection of arm.h to use cpu-features on Android.