================================================================================
Version: 3.3.13
Patch: 00
Date: 2022-02-22
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------

Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant 
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring 
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for 
much more granular output controls. The legacy -Ga showing 
Display/Screen/Monitors is now split apart, and can now work for some features 
in and out of display.

This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.

--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:

If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can 
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl 
5.14 (unless for some reason your distro removed that module from Core Modules).

Basically inxi will simply look for whichever of the 3 is installed, and use 
that one. 

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. The free drivers for xorg like amdgpu, modesetting, alter the the internal 
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the 
ideal role of any ID is to be an identifier that always works. Due to this 
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping 
that this issue does not exist on Wayland compositors.

--------------------------------------------------------------------------------
BUGS:

1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as 
part of Code fix 1.

--------------------------------------------------------------------------------
FIXES:

1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container 
for its data. This would only impact -y 1 or json and xml output cases, and would 
be subtle, but it was an oversight.

2. Small fix for monitor dimensions, failed to switch the mm dimensions for 
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.

3. For Xvesa:

* Show vesa as display driver, Xvesa == vesa, dugh,lol.

* Show better Interface and Screen resolution data missing messages.

* See FIX 5 for adding in display-ID:.

* Show TinX Xvesa string for server data, not just Xvesa.

4. For Wayland, which currently has no EGL support in inxi, if no glxinfo 
present, show EGL Wayland specific Messsage: for advanced EGL data, not the 
generic glxinfo that were shown previously.

5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found 
and that exists. I hadn't realized how much was depending on those x tools, 
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.

6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.

7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.

8. Failed to detect or get Xfree86 X server version number.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1. Extensive Graphics Upgrades:

* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx. 
amdgpu supports this, I believe it's the only one, but don't know for sure.

* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a 
closed laptop screen with attached moniitor), and empty ports on devices. Not 
tested for USB yet.

* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off 
(off is connected but disabled) and empty (linux only).

* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg 
screen and display data. Now it will show most of the data if xrandr is 
available, and all if xrandr and xdpyinfo are installed. More granular error 
messages as well.

* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts. 
Works roughly the same as Screen: s-res: does, except since Wayland has no 
'Screen' concept, that goes into Display. This is sort of a rough algo, 
basically it takes either the dimensions of the total of x and y resolutions, or 
the greatest x or y resolution found for any monitor, whichever is greater, and 
uses that to create the display rectangle resolution composite value.

* -G Display, Monitors: Extended display tool options from just xrandr to 
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or 
gnome-shell and mutter data.

*. -S, -G: compositors, full redo of list, now supported: 

asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm 
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong 
inaban japokwm kiwmi kwinft  labwc laikawm lipstick liri mahogany marina maze 
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr 
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox 
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros 
westford weston wio+ wio wxrc wxrd xuake

* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:

  * X - OpenGL, requires glxinfo , same as before.

  * Wayland - EGL, currently no tool available, stub in place. Allegedly this 
  data can be found but have no idea how or if a tool does that yet

  * Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data 
  samples; v:, source:, dac: (no idea what it is, show it though), controller:, 
  and ram: items. 

  This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
  and Puppy TinyX as well if those projects are still around.

* -G Display/Screen/Monitor data: Created structures and abstractions that allow 
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or 
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan, 
heh.

* -G Display server: For Xvesa, added type TinyX to server if detected. Added 
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:

  server: X.org
    v: 1.20.14
    with: Xwayland 
      v: 21.01
  
Otherwise shows:

  server: Xwayland 
    v: 21.01

* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected 
running, not common, but could happen, shows all detected compositors.

  Display: x11
    server: X.Org
      v: 1.20.13
    compositors:
      1: Mutter
        v: 41.1
      2: xfwm
        v: 4.16.1
    driver:
      X:
        loaded: modesetting
      gpu: radeon

* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:

  Display: x11
    server: X.Org
      v: 1.20.13
    driver:
      X:
        loaded: modesetting
      gpu: radeon
    resolution:

* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either 
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0 
positioned monitor. Position is based on the row and column number in the 
rectangular grid of monitors when monitors per Xorg Screen are > 1. 

For most common multi-monitor layouts, text positions are used, which are in 
general more clear and easy to understand than their internal numeric 
counterparts, that is, unless the layout is too complicated, it will show left, 
or top-left, instead of 1-1, and so on.

Text mode positions are available for the following grid styles currently: 1x2, 
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row, 
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is 
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2), 
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c', 
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center', 
'top-right' complete the possible values. 

If the grid of monitors is greater than the supported rows or columns, it will 
switch to numeric row-column mode, with column-row numbering starting at 1-1, 
top left.

* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the 
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show 
mapped: to show the /sys id.

* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode 
found). Shows hz:

* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.

2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.

3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max 
speed / lanes if different than current speeds/lanes. Note that for unknown 
reasons not all devices in a PCIe slot show this data.

4. -Ixx: terminals added: foot, ate

5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5 
for more info on how this change was done.

6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar, 
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar

7. Added a Tyan board IPMI sensor data set.

8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.

9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their 
warren, endlessly, a stream that is the life essence itself... or something.

--------------------------------------------------------------------------------
CHANGES:

1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as 
well now to explain which tool or tools missing caused the missing data.

2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi, 
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.

3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic 
mode output, which it should have always done, unless -G is also explicitly 
added.

4. Split apart x-server version to v:, which should always have been the case.

5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.

6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.

7. Changed -G drivers to show subsections for X and gpu drivers, and updated 
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.

--------------------------------------------------------------------------------
DOCUMENTATION:

1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G, 
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.

2. Updated -Ga for xrandr/xdpyinfo changes.

3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.

4. Reorganized and added complete table of contents to docs/inxi-data.txt

--------------------------------------------------------------------------------
CODE:

1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based 
on how it's now done for monitor layouts, which is more efficient, use a scalar 
to hold a reference to the array, that avoids having the array ever exist in 
more than 1 place. Part of the ongoing process of avoiding extra hash and array 
copies globally. 

2. Moved to consistent undef behaviors. 
 * For lists of variables use () to undefine, changed all of the the following: 
    1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
    2. (@a,$b,$c,%d) = (undef);
    3. (@a,$b,$c,%d) = undef;
   to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
   Note that assigning undef to @a in the first example creates an array of 1 
   key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
   indexes, or something like that. Not what was wanted.
   Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and 
   undefine the others variables in the list. This was not the desired behavior!
 * For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
 * For some hash and array index values, use $h{a} = undef. These cases may want
   the key itself to exist, with the value of undef, though I believe: 
    undef $h{a};
   is synonymous, but still have to verify that. 

I did some testing, and realized that some of the undef I had used in the 
various previous ways of using undef were not actually resulting in the expected 
behaviors.

3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and 
display_data_xrandr, which allows for more granular handling of those 
dependencies, now inxi can show most advanced display data with only xrandr
installed.

4. Significantly improved all error handling and missing data for Wayland/Xorg.

5. Refactored get_display_manager() to better handle corner case dm file or 
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some 
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.

6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list 
to ps_gui data to get detected compositor[s], much simpler, far more efficient 
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if 
available.

7. With 6. also significantly simplified and optimized get_ps_de_data() for 
desktop data, that's the ps aux fallback case for wm desktop detections. 

8. Made $wl compositors list global to avoid having to update each section, 
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set 
in ps_gui() on initial load.

7. Settled on one and only way to do multiline conditionals, now use no space, 
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not 
try, and leave it up the code flow to show when it's wrapped condition tests.

8. Refactored previous gl_output, expanded it to handle all interface types, 
OpenGL, EGL (not currently active due to no known tool to get EGL data for 
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the 
breaking apart of the X.org centric logic for Display, Monitors, and GL data, 
and make all sections now fully agnostic to display server or protocol type. 

Should new display servers appear, it will now be far more simple to add support 
for them, since they would just plug into the existing abstraction layers.

9. Added --debug-arg to allow for passing specific custom args to the debugger.

10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.

--------------------------------------------------------------------------------
-- Harald Hope - Tue, 22 Feb 2022 15:30:24 -0800

================================================================================
Version: 3.3.12
Patch: 00
Date: 2022-01-18
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------

Small point release with some useful fixes, some bugs corrected, small 
enhancement.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. Note on KNOWN ISSUES 2 from 3.3.10, I realized that the second level 
indentation actually takes care of that hanging parent, since now it's quite 
clear that its children are indented on the following line. So that issue took 
care of itself.

--------------------------------------------------------------------------------
BUGS:

1. In $bsd_type cases, specifically SunOS triggered this, where sysctl was not
present (which it always is in all other BSD types), it tripped an error due to
failure to update to revised $alerts{'sysctl'}->{'message'}, instead was using
the old method. Failed to update that in refactor of CheckTools logic. Would
impact no supported operating systems, but is a bug.

2. Corner case, a combination I never used, inxi -a, triggers error in the RAID 
logic because the mdadm test was not run, generating an undefined eq error. Only
happened when mdraid was present and used on system.

3. Tiny bug, for st+mt cpus, like alder lake,  was printing out second tpc by 
accident which made it look like it said st: 4 tpc: 2. Just a small output
glitch.

--------------------------------------------------------------------------------
FIXES:

1. Added some fallback 32 bit system tests, [2345]86, like i386, i686.

2. Changed shell: Unknown Shell to shell: N/A, that was a legacy use, and was
obviously redundant. N/A is more consistent with rest of output no value found
handling. Due to requirement of doing empty tests, this is set in the data, not
output, generator component.

3. Refactored partition data logic to get rid of bsd tests for df -kTP, -kT, -k.
Now tests only to see if returns data, cascades down until it gets something. 
Now will attempt to reconnect hanging lines when no -P feature available prior 
to main partition data processing. This makes it agnostic to os issues, and it
just pays attention to feature support. 

Also adds in dynamic column count instead of hard-coded, this avoids oddities
and future proofs to some degree. Now systems will adapt seamlessly if support
for -P appears, or -T, or whatever.

4. Partitions corner case, where has zram, but has no partitions, failed to show
partitions no data found message since @partitions had data in it, but nothing
for partitions output to print. Seen in TinyCore for example, but might happen 
in other ram based systems.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1. Added Slint to distro ID, and slint/slackware to system base.

--------------------------------------------------------------------------------
CHANGES:

1. None

--------------------------------------------------------------------------------
DOCUMENTATION:

1. Typo in man page fixed.

2. A few more edits and corrections on 3.3.10 changelong. That thing was written 
concurrently with the development, and thus had lingering errors when things 
were changed in midstream.

--------------------------------------------------------------------------------
CODE:

1. Added --cygwin and --android fake system type flag. Switches on $b_android/
$b_cygwin flags.

--------------------------------------------------------------------------------
-- Harald Hope - Tue, 18 Jan 2022 14:02:54 -0800

================================================================================
Version: 3.3.11
Patch: 00
Date: 2021-12-16
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------

Quick bug fix release. With as many changes as we got in 3.3.10, there were 
bound to be a handful of oversights that were not caught in testing simply 
because those hardware scenarios were not present in the tested systems.

Also minor feature enhancement for CPU scaling min/max speeds.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. Due to the huge amount of changes, and the speed of change, while the new 
code is working as intended, it's somewhat lacking in coding elegance since a 
lot of it was hacked out very quickly, in near real time. This will get cleaned 
up and refactored to be less redundant if it does not impact execution speed, 
but is not pressing since there should be no functional difference.

--------------------------------------------------------------------------------
BUGS:

1. Tiny oversight, in single case CPU model id would fail because it was using
an undefined test from previous tests, not the right test, that is. Tripped
error on Elbrus for example.

2. Typo in battery secondary type status, created undefined value error. This 
was a recently created bug.

--------------------------------------------------------------------------------
FIXES:

1. PPC revision change broke Elbrus revision test for stepping. Added in more
tests to show stepping for elbrus revision.

2. Single core Elbrus in cpuinfo fallback mode failed to assign core multiplier
so L1 cache failed.

3. In cpuinfo fallback mode, Elbrus E2C3 cache data failed to appear, that data
is not per block in cpuinfo, but is the last block, so those tests had to run 
on each block, not just the first one.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1a. Show for -Ca scaling min/max speeds if different from CPU min/max speeds.

1b. If no cpuinfo_min/max_freq speeds found, and scaling_min/max_freq found, set
overall min/max to use scaling min/max instead of cpuinfo min/max.

--------------------------------------------------------------------------------
CHANGES:

1. None.

--------------------------------------------------------------------------------
DOCUMENTATION:

1. Cleaned up and proofread better 3.3.10 changelog, it had a lot of errors 
because stuff kept changing.

--------------------------------------------------------------------------------
CODE:

1. Small code optimizations.

--------------------------------------------------------------------------------
-- Harald Hope - Tue, 16 Dec 2021 16:14:08 -0800

================================================================================
Version: 3.3.10
Patch: 00
Date: 2021-12-13
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------

Huge refactor of CPU physical/core/cache logic. That was some very old logic 
with a lot of hacks and patches, but it had never been actually rewritten to 
take advantage of Perl's far more powerful and robust data structures and logic. 
This caused a continuous stream of error cases in subtle ways, or not so subtle, 
and fixes were just changing how the errors manifested.

Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.

Note Changes 5, change of default widths in display to 80 columns, and out (aka, 
console, or ssh into remote system), 100. You can still use other widths if you 
like something wider using the configuration options shown. Also upped max 
columns wrapping line starters to own rows to 110 columns from 90, again the 
idea being to make output more readable to other users when posted in public.

I've been thinking of this change for a long time, but was hoping -y would 
register with users, but it hasn't gained enough traction, so the result is way 
too many super hard to read issue reports, forum posts, linux kernel issues, 
etc, it's honestly gotten sort of embarrassing because they make it look like 
inxi has bad output. Sidescrolling code blocks in forums in particular are 
absurdly hard to read and scan rapidly for data.

Going along with the width and indentation changes, for most main row types, if 
they wrap to a second row, they are further indented 2 columns, to make it 
easier to see what they belong to. The two levels of indentation contain more 
useful visual cues as to what belongs to what.

There was a temptation to release this as either 3.4.00 or 4.0.00 but in the 
end, I decided to follow the numbering rules, and to just roll it to 3.3.10 
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.

I hope this refactor meets its primary goals, and that the new defaults for 
display help resolve public posting issues which have grown increasingly 
annoying for anyone trying to read those pasted in too long outputs.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.

2. [See KNOWN ISSUES 2 for 3.3.12 above] In some instances, the parent key:value 
pairs with '' as value, those are parents of children key:value pairs, are left 
hanging at end of line, with the children on the following line. This can look 
awkward, but in other cases, actually looks very good, it depends if it's at the 
start or end of the line.

I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.

It's tricky though, because in cases where it's the first item on the line, you 
want that behavior, but when it's last, you don't. But this may be worth 
revisiting in the future.

3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.

4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq, 
per thread/core, which really adds up on high thread count CPUs. There is a 
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are 
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...

This is a drag, and really looks like a kernel bug, or a frequency driver bug.

--------------------------------------------------------------------------------
BUGS:

1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon 
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was 
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to 
more than 1 core, except for using a crude hack for AMD Bulldozer microarch. 
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores 
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel 
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST 
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.

2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this 
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu 
arch. 

3. In a related bug, hex to decimal tool used to create --admin hex/decimal 
output for family/model/stepping was also not testing if the string was an 
actual valid hex number. Case in particular, power pc with revision field 
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.

4. Long standing bug found while doing Change 5: inxi actually never applied 
separate in/out of dispay to widths because using a legacy boolean that was not 
updated, so it was always using out of display widths.

--------------------------------------------------------------------------------
FIXES:

1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].

2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver. 
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.

3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.

4. In cases where bogomips were 0 due to false values in risc results, show N/A.

5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache. 

6. Added failsafe tests for stepping and model id before doing conversion to 
hex. Make sure integer!

7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how 
it goes.

8. Made bogomips tests more granular, now only rejects low sub 50 bogomips 
values if %risc cpu type. Legacy ancient cpus like 486 could and did have 
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html

9. See Enhancement 12 as well. If OpenBSD, which has no per core data or 
physical cpu data, is running on MT capable cpu, but for security OpenBSD has 
disabled MT, will now force MT to be not shown via the hw.smt value. This 
removes a small glitch that would have bothered OpenBSD users who know that 
OpenBSD has disabled MT for security purposes.

10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that 
was flat out dumb, since we can just use dmidecode type 4 to iterate physical 
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1 
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the 
found counts with the dmidecode physical cpu counts.

11. Corrected bad assumption that threads would always be 2 per core for MT 
tests. Revised logic should handle this case fine now, and show correct thread 
count per core.

12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.

13. Fixed case when key: value first word plus other parts of line longer than 
max width, failed to wrap as expected.

14. Added start/end ' and " to existing start / end \s trims to main filters.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing 
sudo/root, and it will be more accurate than ever before.

2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical 
processor count * L1/L2/L3 total in parentheses, like: L2: 2x 1.5 MiB (3 MiB).

3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed 
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the 
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than 
the other(s). 

4. CPU: Handles advanced cases of new architectures, like Alder Lake with 
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or 
more different core sets, with different max/min frequencies. Previously a hack 
was used to handle only ARM CPUs with this type of architecture. Will show 
correct CPU core counts, which previous inxi versions would fail to do for Alder 
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT) 
perforance cores.

This should also in theory show different the different min/max speeds if they 
were detected. Those did not seem to be set correctly in Alder Lake sample data 
I saw however, P and E cores were set to the same min/max speeds. 

[Update 3.3.12: more research suggests that for now, 1 cpu physical body will 
contain one clock generator, so that is not a mistake. Future CPUs may add a 
second clock generator but that is probably very complicated to implement, which 
is why ARM complex cpus simply use two cpus, with different clock rates when 
they want to run different speeds for efficiency.]

5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing), 
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU 
that has this type of complex topology that has been dynamically detected, like 
Alder Lake or different core count or min/max speed RISC CPUs.

6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per 
physical CPU, as with Alder Lake, but also many other variants that were poorly 
or not at all handled before, how many of each cache type (L1 Data, instruction) 
were found, otherwise will show how many of each cache were found. 

7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with 
different core types in one physical CPU (type: MST AMCP), the number that are 
single threaded (st) and number that are multi-threaded (mt).

8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now 
it's easy to add this type of support.

9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.

10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data, 
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.

11. For -Ca, full CPU topology report if any complex topogy is detected, 
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no 
point in wasting a line for something with no more data than the short string. 
Complex types include MT CPUs since they will have different thread counts etc, 
and will have 2 or more threads per core, which will also be listed. 

12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology 
section, can be useful for systems with disabled MT, but supporting it. If no 
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after 
'type:' section, and enabled if -Cxxx (since MT really already tells you that).

13. For -Ca Speed: report, added scaling: report, with childrend 'governor:'. 
Can show 1 or more active governors. Also shows scaling driver:. Shows if either 
is available.

scaling:
  driver: ..
  governor: ..
  
These may be quite useful over time to help diagnose or debug scaling issues.

14. Output height (in lines) control: -Y [-3|-2|-1|0|1-xxx]]. This lets you 
break up any of the output into whatever number of lines you want. Also useful 
out of DISPLAY for reading -h options menu items etc.

It came tp my attention that the long standing shift+pgup/pgdown (aka 
'softscrollback) behavior had stopped working in kernel framebuffer mode, and in 
fact has been removed from the current Linux kernel, at least until it is 
rewritten to be more clean and understandable. Read more about it in these 
kernel post/commit messages:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/

Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Do not remove color codes when piped or redirected. Mostly useful for 
         piping to less -R, to preserve color codes.
* -Y -3: Restore default unlimited height if LINES_MAX configuration item used.

15. And finally, more disk vendors/vendor ids. As usual. As expected.

--------------------------------------------------------------------------------
CHANGES:

1. If /sys or /proc/cpuinfo speed data available: 
* For -b CPU item:
   speed: [speed MHz] min/max: [min]/[max] MHz
  becomes:
   speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item 
   Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
  becomes:
   Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.

For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1. 

2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed 
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even 
dual core CPUs, but makes little sense today with many core/threaded cpus.

With -x, it will show the high: [speed] item as well, after 'avg:'.

3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!

4. Going along with Fix 5, give up on trying to pretend we can guess at L2 
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
 note: check
 
and call it a day.

5a. Change default width to 80 columns in display, and 100 and out. Too many 
users are posting horribly wrapping inxi output in forums, issue trackers, etc, 
and it frankly makes inxi look really bad, creates awful side scrolling code 
boxes, etc. So now default widths in and out of console are 80/100 (since often 
data is generated in SSH or out of X/Wayland) for issues. 

This essentially makes -y 80/-y the default width in display, and a wrapped 100 
out. This is what I've been using for a few years now, and after seeing far too 
many side scrolling or badly wrapping inxi outputs online, I think it's probably 
time to just force 80 column widths as default and call it a day.

You can change these new defaults using configuration options (these are the 
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):

 COLS_MAX_CONSOLE=115 # in display, terminal client max width 
 COLS_MAX_IRC=100 
 COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
 
5b. Made second and greater rows of a line indent +2 to make it more clear that 
it is a child row of its parent row. Note that because no arg short form and -I 
are special types of rows, this behavior is not used, they just print out as 
usual. This makes for more readable and easy to follow flow of output data.
 
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core 
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.

7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not 
particularly important bit of data afterall.

8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.

9. Removed CPU die for -Cxx, that's only going to show with -Ca now.

10. If -Ca, and if certain complexity conditions are met, shows a separate 
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.

11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output. This places bogomips at end of Speed: line, after the core speeds.

12. Flags/Features now shows in the same place, under Speeds: always, whether 
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.

--------------------------------------------------------------------------------
DOCUMENTATION:

1. Updated man/help for new CPU extra data options and output changes. 

2. Cleaned up and added sample outputs for man CPU items. 

3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than 
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support 
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.

4. Added documention items for INDENT (--indent), INDENTS (--indents).

5. Re-ordered help menu and man page, created new Filters and Output Controls 
sections to make stuff easier to find. In man page, also added on top a list of 
OPTIONS sections to make finding stuff easier.

--------------------------------------------------------------------------------
CODE:

1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status(); 
set_cpu_speeds_sys(). get_caches() was only a placeholder for the full featured 
cpu_sys data source, and was removed; cpu_speeds() no longer needed, integrated 
into other logic; cpu_dies_sys() removed, integrated into other logic.

This logic is now integrated into cpu_data_sys() data generator.

2. Changed the main CpuItems functions to use array/hash references, not passing 
full hashes or arrays in most cases now.

3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then 
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the 
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.

4. New tools: 
* get_defined() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any 
combination of those, like 3,6,12-29

5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.

6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.

7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo 
issues.

8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot 
easier since inxi can either test for %risc defined, or for a specific type of 
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which 
got rid of a lot of tests. Also made all risc tests consistent, some were ARM 
only, or arm/mips, but were supposed to be for all risc cpus.

13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.

10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx, 
and row_defaults() to message().

11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method 
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests 
pointlessly.

12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.

--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800

================================================================================
Version: 3.3.09
Patch: 01
Date: 2021-11-22
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------

Thanks manjaro user alven for finding a bunch of corner and not so corner case 
errors, glitches, documentation oversights, etc.

This is a point release between the coming full CPU refactor and the current
set of bug fixes and issue handlings.

This release also contains the debuggers for the new CPU data logic, which are
important to get this CPU refactor stable and reliable across old/new systems,
different operating systems and platforms.

Wanted to do this intermediate releaase to get the current fixes out, which 
make inxi overall better for CPU issues, but do not handle the core requirement
to do a full refactor.

--------------------------------------------------------------------------------

CORRECTION:

1. On release notes for 3.3.08: due to a long delay to get real debugger data 
from the person who had the issue, but finally getting it after the release of 
3.3.08, there was NO bug in ps wwaux output. Something else was creating the 
linewraps, maybe the subshell, it's basically impossible to know since we never 
got a real debugger data set, which is the only real way to get the actual same 
data inxi will see. 

Was it a subshell wrapping the output? We just can't know, nor are we likely to 
ever find out.
