From: ThomasKaiser Date: Sat, 21 Jan 2023 17:03:11 +0000 (+0100) Subject: Add 53/002:Samsung Exynos-m3 X-Git-Tag: v2.39-rc1~126^2~7 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cf922cbe1ab4076ce069db7d065e3653f55db1d1;p=thirdparty%2Futil-linux.git Add 53/002:Samsung Exynos-m3 ID 002 for the Exynos-m3 core seems weird since Exynos-m1 had 001 but Samsung's Mongoose line differs only by stepping between M1 and M2 * Mongoose 1, for example [Exynos 8890](https://github.com/ThomasKaiser/sbc-bench/blob/master/results/Exynos-8890-highperformance.cpuinfo): Exynos-m1 / r1p1 * Mongoose 2, for example [Exynos 8895](https://github.com/ThomasKaiser/sbc-bench/blob/master/results/Exynos-8895.cpuinfo): Exynos-m1 / r4p0 * Mongoose 3, for example [Exynos 9810](https://github.com/ThomasKaiser/sbc-bench/blob/master/results/Exynos-9810.cpuinfo): Exynos-m3 / r1p0 --- diff --git a/sys-utils/lscpu-arm.c b/sys-utils/lscpu-arm.c index b30e0e7546..78b4d677bb 100644 --- a/sys-utils/lscpu-arm.c +++ b/sys-utils/lscpu-arm.c @@ -145,6 +145,7 @@ static const struct id_part qcom_part[] = { static const struct id_part samsung_part[] = { { 0x001, "exynos-m1" }, + { 0x002, "exynos-m3" }, { -1, "unknown" }, };