public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-announce@cygwin.com
Subject: Updated: cpuid 20201006
Date: Sat, 10 Oct 2020 22:23:10 -0600	[thread overview]
Message-ID: <f5ed2f5a-a1ce-68b4-dfcb-457d62dfd093@SystematicSw.ab.ca> (raw)

The following package has been updated in the Cygwin distribution:

* cpuid 20201006

The program displays detailed information about the CPU(s) gathered from
the CPUID instruction, and also determines the exact model of CPU(s).

Whereas /proc/cpuinfo is like an abstract of the features important to
Linux in a system, cpuid is a standalone utility which writes a paper
expounding on every feature in each CPU's architecture and what it can
do, at about the one line per bit level.

It is updated and released frequently and appears current with Intel and
AMD info and supports other vendors' chips.

Changes

Added latest Intel and AMD features and added, corrected, or clarified
(synth) decoding for:

* Intel (0,6),(10,6) Comet Lake, Rocket Lake, Elkhart Lake B0, Alder
  Lake [Golden Cove], (0,6),(8,10) Lakefield, Tiger Lake-U B0 stepping,
  Comet Lake-H/S Core i*-10000;

* AMD (7,5),(2,6) Cato, (8,15),(2,0) Dali, Dali A1 stepping, Picasso A1
  stepping, Renoir A1 stepping, (8,15),(2,0) Picasso;

* Zhaoxin KX-6000 that still claims the vendor CentaurHauls;

Detect bogus 0x20000000 leaf values and cap the maximum valid register
to avoid absurdly long dumps on old CPUs.

See the project home page for more information:

	http://etallen.com/cpuid.html


                 reply	other threads:[~2020-10-11  4:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f5ed2f5a-a1ce-68b4-dfcb-457d62dfd093@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).