From: "Anthony PERARD" <anthony.perard@citrix.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Zeng, Star" <star.zeng@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
Julien Grall <julien.grall@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [edk2-devel] [PATCH 0/4] Define SERIAL_DXE_FILE_GUID only once
Date: Mon, 3 Jun 2019 11:24:57 +0100 [thread overview]
Message-ID: <20190603102457.GE2126@perard.uk.xensource.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9D2254E@ORSMSX113.amr.corp.intel.com>
On Sat, Jun 01, 2019 at 05:00:37PM +0000, Kinney, Michael D wrote:
> I am curious. I agree that a GUID can be defined in DEC file and
> in an include file that is used as a Vendor GUID in a device path.
>
> Is there any reason that the FILE_GUID for the module needs to be
> the same GUID value? Is there any code that looks for an FFS file
> with that GUID value as the FFS file name?
Sorry, I think you lost me here. The way I see it is that the GUID is
"produced" only by "MdeModulePkg/Universal/SerialDxe/SerialDxe.inf",
and then all the "PlatformBootManagerLib" are looking for exactly that
driver (SerialDxe), so the FILE_GUID is used.
There is probably a reason why this is already done three times in the
edk2.git repo.
Maybe you could have a closer look at
"ArmVirtPkg/Library/PlatformBootManagerLib/PlatformBm.c" to see how
SERIAL_DXE_FILE_GUID is used.
BTW, I've added "gSerialDxeFileGuid" as it seems there's often both a
"#define" and a variable for the GUID, but only the "#define" is used so
far. So maybe I should remove the variable?
> If not, then it would be better to not over use that GUID value.
> The FILE_GUID of the SerialDxe can be different.
Thanks for the review,
--
Anthony PERARD
next prev parent reply other threads:[~2019-06-03 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 11:37 [PATCH 0/4] Define SERIAL_DXE_FILE_GUID only once Anthony PERARD
2019-05-29 11:37 ` [PATCH 1/4] MdeModulePkg: Add SERIAL_DXE_FILE_GUID Anthony PERARD
2019-05-29 11:37 ` [PATCH 2/4] ArmVirtPkg/PlatformBootManagerLib: Use SERIAL_DXE_FILE_GUID from MdeModulePkg Anthony PERARD
2019-05-29 11:37 ` [PATCH 3/4] ArmPkg/PlatformBootManagerLib: " Anthony PERARD
2019-05-29 11:37 ` [PATCH 4/4] UefiPayloadPkg/PlatformBootManagerLib: " Anthony PERARD
2019-05-31 9:12 ` [edk2-devel] [PATCH 0/4] Define SERIAL_DXE_FILE_GUID only once Ard Biesheuvel
2019-06-01 8:26 ` Zeng, Star
2019-06-01 17:00 ` Michael D Kinney
2019-06-03 10:24 ` Anthony PERARD [this message]
2019-06-03 12:01 ` Laszlo Ersek
2019-06-03 14:50 ` Michael D Kinney
2019-06-03 16:31 ` Laszlo Ersek
2019-06-03 17:06 ` Michael D Kinney
2019-06-06 12:33 ` Anthony PERARD
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=20190603102457.GE2126@perard.uk.xensource.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