From b35054355994cae0ce0561b80df38217b65397d5 Mon Sep 17 00:00:00 2001
From: Unit 193 <unit193@unit193.net>
Date: Sat, 7 Sep 2024 17:59:41 -0400
Subject: New upstream version 3.3.36-1.

---
 inxi.1 | 100 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------
 1 file changed, 83 insertions(+), 17 deletions(-)

(limited to 'inxi.1')

diff --git a/inxi.1 b/inxi.1
index 1c30ffb..43b86b5 100644
--- a/inxi.1
+++ b/inxi.1
@@ -15,7 +15,7 @@
 .\"  with this program; if not, write to the Free Software Foundation, Inc.,
 .\"  51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 .\"  
-.TH INXI 1 "2024\-06-18"inxi" "inxi manual"
+.TH INXI 1 "2024\-09-04" "inxi 3.3.36" "inxi manual"
 
 .SH NAME
 inxi \- Command line system information script for console and IRC
@@ -520,9 +520,9 @@ unless you figure out how to set up doas/sudo to permit dmidecode to read
 \fB/dev/mem\fR as user. 
 
 \fBudevadm\fR can be run by non\-superuser, or if dmidecode is not installed 
-(Linux only). It has a slightly less reliable dmi table outut, and does not seem 
-to support more than 1 board memory array, but is pretty good. Voltages may be 
-wrong however.
+(Linux only). It has a slightly less reliable dmi table output, and does not 
+seem to support more than 1 board memory array, but is pretty good. Voltages may 
+be wrong however.
 
 Both \fBdmidecode\fR and \fBudevadm\fR need a DMI table with RAM data to create 
 the report. Most SBC/SOC boards don't have dmi based RAM data. But most other 
@@ -2105,17 +2105,25 @@ common).
 to this line from \fBInfo:\fR line. 
 
 Topology line contains, if available and/or relevant: physical CPU count 
-(\fBcpus:\fR); per physical cpu core count (cores:\fR); threads per core, if > 1 
-(\fBtpc:\fR); how many \fBthreads:\fR (if more threads than cores); \fBdies:\fR 
-(rarely detected, but if so, if > 1); smt status (if no smt status found, shows 
-\fBN/A\fR). 
-
-If complex CPU type, like Alder lake, cores; will have a more granular breakdown 
-of how many mt (multi\-threaded) and how many st (single\-threaded) cores there 
-in the physical cpu ( \fBmt\-cores:\fR, \fBst\-cores:\fR);  For complex CPU 
-types like ARM SoC devices with 2 CPU types, with different core counts and/or 
-\fBmin/max:\fR) frequencies, \fBvariant:\fR per type found, with relevant 
-differences shown, like \fBcores:\fR, \fBmin/max:\fR, etc. 
+(\fBcpus:\fR); per physical CPU \fBdies:\fR, \fBclusters:\fR, \fBcores:\fR; 
+threads per core, if > 1 (\fBtpc:\fR); how many \fBthreads:\fR (if more threads 
+than cores); smt status (if no smt status found, shows \fBN/A\fR). 
+
+Not all CPUs have or report dies or clusters. Some may have dies but no 
+clusters, some clusters but no dies, some dies and clusters, and some neither 
+dies nor clusters. This is a function of how the CPU topology reports itself to 
+the kernel. Note that core counts are per physical CPU, not per die or cluster. 
+Clusters are per die, and in cases of > 1 dies, will show as: \fBclusters: 
+2x4\fR.
+
+If complex CPU type, like Alder lake, \fBcores:\fR will have a more granular 
+breakdown of how many mt (multi\-threaded) and how many st (single\-threaded) 
+cores there are in the physical cpu (\fBmt\-cores:\fR, \fBst\-cores:\fR);  For 
+complex CPU types like ARM SoC devices with 2 CPU types, with different core 
+counts and/or \fBmin/max:\fR) frequencies, \fBvariant:\fR per type found, with 
+relevant differences shown, like \fBcores:\fR, \fBmin/max:\fR, etc. 
+
+
 
 .nf
 \fBCPU:
@@ -2135,10 +2143,10 @@ differences shown, like \fBcores:\fR, \fBmin/max:\fR, etc.
     microcode: 0x8001250
   Topology:
     cpus: 2
+      dies: 4
       cores: 16
-        tpc: 2
       threads: 32
-      dies: 4
+        tpc: 2
    cache:
      L1: 2x 1.5 MiB (3 MiB)
        desc: d\-16x32 KiB; i\-16x64 KiB
@@ -2161,6 +2169,64 @@ differences shown, like \fBcores:\fR, \fBmin/max:\fR, etc.
     bogomips: 267823\fR
 .fi
 
+Or this Raptor Lake with 1 die, 4 clusters, and efficiency and perforance cores:
+
+.nf
+\fBCPU:
+  Info:
+    model: 13th Gen Intel Core i5-1345U
+    bits: 64
+    type: MST AMCP
+    arch: Raptor Lake
+    level: v3
+      note: check
+    built: 2022+
+    process: Intel 7 (10nm)
+    family: 6
+    model-id: 0xBA (186)
+    stepping: 3
+    microcode: 0x411C
+  Topology:
+    cpus: 1
+      dies: 1
+      clusters: 4
+      cores: 10
+      threads: 12
+        mt: 2
+          tpc: 2
+        st: 8
+    smt: enabled
+    cache:
+      L1: 928 KiB
+        desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB
+      L2: 6.5 MiB
+        desc: 2x1.2 MiB, 2x2 MiB
+      L3: 12 MiB
+        desc: 1x12 MiB
+  Speed (MHz):
+    avg: 1535
+    high: 2820
+    min/max: 400/4700:3500
+    scaling:
+      driver: intel_pstate
+      governor: powersave
+    cores:
+      1: 0
+      2: 400
+      3: 429
+      4: 926
+      5: 1244
+      6: 1139
+      7: 2680
+      8: 1021
+      9: 2582
+      10: 2744
+      11: 2820
+      12: 2445
+    bogomips: 59904
+  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx\fR
+.fi
+
 \- Adds CPU Vulnerabilities (bugs) as known by your current kernel. Lists by 
 \fBType: ... (status|mitigation): ....\fR for systems that support this feature 
 (Linux kernel 4.14 or newer, or patched older kernels).
-- 
cgit v1.2.3