Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <Randy.MacLeod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] dmidecode: Upgrade 3.6 -> 3.7
Date: Fri, 19 Dec 2025 12:54:27 -0500	[thread overview]
Message-ID: <20251219175427.2176895-1-Randy.MacLeod@windriver.com> (raw)

From: Randy MacLeod <Randy.MacLeod@windriver.com>

From NEWS:
Version 3.7 (Thu Dec 18 2025)
  - [COMPATIBILITY] Use binary unit prefixes.
  - [COMPATIBILITY] Rename BIOS to Firmware.
  - [PORTABILITY] Improve variable declarations.
  - [PORTABILITY] Stop open-coding the u64 type.
  - [PORTABILITY] Use unaligned memory accesses unconditionally.
  - [PORTABILITY] No longer build with -Winline.
  - Support for SMBIOS 3.8.0. This includes a new processor family.
  - Support for SMBIOS 3.9.0. This includes chassis type name adjustments,
    new rack attributes, slot ID for more slot types, and new memory device
    form factors and types.
  - Decode HPE OEM records 193, 195, 202, 211, 226, 229, 232 and 244.
  - Update HPE OEM records 203, 216, 242 and 245.
  - EDSFF slot names now include their .S/.L suffix.

Tested on qemux86/kvm:
   root@qemux86-64:~# dmidecode
   # dmidecode 3.7
   Getting SMBIOS data from sysfs.
   SMBIOS 2.8 present.
   9 structures occupying 401 bytes.
   Table at 0x000F52B0.
   ...

Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
---
 .../dmidecode/{dmidecode_3.6.bb => dmidecode_3.7.bb}            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/dmidecode/{dmidecode_3.6.bb => dmidecode_3.7.bb} (89%)

diff --git a/meta/recipes-devtools/dmidecode/dmidecode_3.6.bb b/meta/recipes-devtools/dmidecode/dmidecode_3.7.bb
similarity index 89%
rename from meta/recipes-devtools/dmidecode/dmidecode_3.6.bb
rename to meta/recipes-devtools/dmidecode/dmidecode_3.7.bb
index e5b4e27687..93c3678d9a 100644
--- a/meta/recipes-devtools/dmidecode/dmidecode_3.6.bb
+++ b/meta/recipes-devtools/dmidecode/dmidecode_3.7.bb
@@ -18,4 +18,4 @@ do_install() {
         install
 }
 
-SRC_URI[sha256sum] = "e40c65f3ec3dafe31ad8349a4ef1a97122d38f65004ed66575e1a8d575dd8bae"
+SRC_URI[sha256sum] = "2c3aed12c85a1e6a9410d406d5e417c455466dc1bc7c89278bb32cf7cad91e8a"
-- 
2.34.1



                 reply	other threads:[~2025-12-19 17:54 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=20251219175427.2176895-1-Randy.MacLeod@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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