From: Tom Rini <trini@konsulko.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: u-boot@lists.denx.de, u-boot-amlogic@groups.io
Subject: Re: [PATCH] libretech-cc: Populate SMBIOS information
Date: Tue, 21 Nov 2023 08:15:51 -0500 [thread overview]
Message-ID: <20231121131551.GP2513409@bill-the-cat> (raw)
In-Reply-To: <a653e096-cf28-4573-856f-d52dae233b46@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On Tue, Nov 21, 2023 at 10:18:04AM +0100, Neil Armstrong wrote:
> Hi Tom,
>
> On 20/11/2023 21:16, Tom Rini wrote:
> > Enable CONFIG_SYSINFO_SMBIOS and populate the nodes so that Linux can
> > eventually display this information
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > Posting this as this was the easiest platform for me to test some SMBIOS
> > related patches on and I needed to populate the nodes so I could check
> > things in dmidecode once Linux was up.
>
> Sorry to be late a the party, but can't this be dynamically found from DT's compatible & model ?
> Since I'll probably need to add this to all boards, it seems like a duplicate of what's already in the DT.
Part of the "fun" as to why we have the binding here is that while we
could use the top-level model property, there's not a corresponding one
for manufacturer. I'm fine ignoring the patch I posted here and having a
longer discussion about populating SMBIOS more usefully, globally, as I
think has been suggested a time or two.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-11-23 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:16 [PATCH] libretech-cc: Populate SMBIOS information Tom Rini
2023-11-21 2:16 ` Simon Glass
2023-11-21 9:18 ` Neil Armstrong
2023-11-21 13:15 ` Tom Rini [this message]
2023-11-21 13:46 ` Neil Armstrong
2023-11-21 14:09 ` Tom Rini
2023-11-21 14:43 ` Neil Armstrong
2023-11-21 15:07 ` Ilias Apalodimas
2023-11-22 20:02 ` Peter Robinson
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=20231121131551.GP2513409@bill-the-cat \
--to=trini@konsulko.com \
--cc=neil.armstrong@linaro.org \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.