From: "Fu, Siyuan" <siyuan.fu@intel.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 0/2] NetworkPkg: Add warning message for PXE if failed to read system GUID from SMBIOS.
Date: Fri, 2 Feb 2018 03:49:28 +0000 [thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B4284D8@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503AAA3E4D@shsmsx102.ccr.corp.intel.com>
Jiewen,
NetLibGetSystemGuid is also used by some other drivers like DHCP6, and it's acceptable to not use system GUID as client identifier in DHCP protocol. That's why I only add the warning in PXE driver.
BestRegards
Fu Siyuan
> -----Original Message-----
> From: Yao, Jiewen
> Sent: Friday, February 2, 2018 11:47 AM
> To: Fu, Siyuan <siyuan.fu@intel.com>; edk2-devel@lists.01.org
> Subject: RE: [edk2] [Patch 0/2] NetworkPkg: Add warning message for PXE if
> failed to read system GUID from SMBIOS.
>
> Hi Siyuan
> It is great idea to add such warning message to help debug such PXE issue.
>
> Do you think it will be better if we add such info in NetLib -
> NetLibGetSystemGuid().
>
> As such, we don't need update all consumers.
>
> Thank you
> Yao Jiewen
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Fu
> > Siyuan
> > Sent: Friday, February 2, 2018 11:29 AM
> > To: edk2-devel@lists.01.org
> > Subject: [edk2] [Patch 0/2] NetworkPkg: Add warning message for PXE if
> failed
> > to read system GUID from SMBIOS.
> >
> > Current PXE driver uses zero GUID if failed to get the system GUID from
> smbios
> > table, and some OS PXE boot may fail in such case. This patch is to add
> a warning
> > message to inform user that smbios table is missed on the platform.
> >
> > Fu Siyuan (2):
> > NetworkPkg: Add warning message for PXE if failed to read system GUID
> > from SMBIOS.
> > MdeModulePkg/PXE: Add warning message for PXE if failed to read system
> > GUID from SMBIOS.
> >
> > MdeModulePkg/Universal/Network/UefiPxeBcDxe/PxeBcDhcp.c | 5 ++++-
> > NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c | 3 +++
> > NetworkPkg/UefiPxeBcDxe/PxeBcImpl.c | 1 +
> > 3 files changed, 8 insertions(+), 1 deletion(-)
> >
> > --
> > 2.13.0.windows.1
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-02-02 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 3:28 [Patch 0/2] NetworkPkg: Add warning message for PXE if failed to read system GUID from SMBIOS Fu Siyuan
2018-02-02 3:28 ` [Patch 1/2] " Fu Siyuan
2018-02-02 3:28 ` [Patch 2/2] MdeModulePkg/PXE: " Fu Siyuan
2018-02-02 3:47 ` [Patch 0/2] NetworkPkg: " Yao, Jiewen
2018-02-02 3:49 ` Fu, Siyuan [this message]
2018-02-02 4:38 ` Yao, Jiewen
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-list 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=B1FF2E9001CE9041BD10B825821D5BC58B4284D8@SHSMSX103.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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