All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH] smbios: Fix calculating BIOS Release Date
Date: Fri, 23 Apr 2021 10:25:21 +0800	[thread overview]
Message-ID: <CAEUhbmWUrpsRExjsHQgpBm9fXVFyJdKfssofM1-yaPVZakmQMg@mail.gmail.com> (raw)
In-Reply-To: <20210422160957.26936-1-pali@kernel.org>

Hi Pali,

On Fri, Apr 23, 2021 at 12:10 AM Pali Roh?r <pali@kernel.org> wrote:
>
> BIOS Release Date must be in format mm/dd/yyyy and must be release date.
> U-Boot currently sets BIOS Release Date from U_BOOT_DMI_DATE macro which is
> generated from current build timestamp.
>
> Fix this issue by setting U_BOOT_DMI_DATE macro to U-Boot version which is
> better approximation of U-Boot release date than current build timestamp.
> Current U-Boot versioning is in format yyyy.mm so as a day choose 01.
>
> Some operating systems are using BIOS Release Date for detecting when was
> SMBIOS table filled or if it could support some feature (e.g. BIOS from
> 1990 cannot support features invented in 2000). So this change also ensures
> that recompiling U-Boot from same sources but in different year does not
> change behavior of some operating systems.
>
> Macro U_BOOT_DMI_DATE is not used in other file than lib/smbios.c
> so remove it from global autogenerated files and also from Makefile.
>
> Signed-off-by: Pali Roh?r <pali@kernel.org>
> ---
>  Makefile                |  2 --
>  doc/develop/version.rst |  1 -
>  lib/smbios.c            | 23 +++++++++++++++++++++++
>  3 files changed, 23 insertions(+), 3 deletions(-)
>

With this change the U-Boot date is only the release date, so one
cannot tell exact BIOS date on which U-Boot was built from.

Regards,
Bin

  reply	other threads:[~2021-04-23  2:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 16:09 [PATCH] smbios: Fix calculating BIOS Release Date Pali Rohár
2021-04-23  2:25 ` Bin Meng [this message]
2021-04-23  8:27   ` Pali Rohár
2021-04-23  9:04     ` Mark Kettenis
2021-04-23  9:14       ` Pali Rohár
2021-06-14 10:19         ` Pali Rohár
2021-07-05 15:55 ` Simon Glass
2021-07-16  6:39 ` Heinrich Schuchardt
2021-07-16  9:56   ` Pali Rohár

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=CAEUhbmWUrpsRExjsHQgpBm9fXVFyJdKfssofM1-yaPVZakmQMg@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --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.