From: "Rebecca Cran" <rebecca@bsdio.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Saloni Kasbekar <saloni.kasbekar@intel.com>,
Zachary Clark-williams <zachary.clark-williams@intel.com>,
Doug Flick <dougflick@microsoft.com>
Subject: [edk2-devel] Hash2DxeCrypto.inf missing from NetworkComponents.dsc.inc (needed for TcpDxe)?
Date: Wed, 30 Oct 2024 21:30:50 -0600 [thread overview]
Message-ID: <df70ddbe-4a4d-4c1a-98cf-729aae7464fc@bsdio.com> (raw)
I noticed a "Driver <GUID> was discovered but not loaded!" message
referring to TcpDxe when booting one of my Arm systems.
Since TcpDxe has a Depex on gEfiHash2ServiceBindingProtocolGuid, do we
need to add Hash2DxeCrypto.inf to NetworkComponents.dsc.inc to allow it
to load?
cc'ing Doug Flick since it looks like he added the dependency on
gEfiHash2ServiceBindingProtocolGuid in May with the CVE-2023-45238 patch.
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120698): https://edk2.groups.io/g/devel/message/120698
Mute This Topic: https://groups.io/mt/109309097/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2024-10-31 3:31 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-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=df70ddbe-4a4d-4c1a-98cf-729aae7464fc@bsdio.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