From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io
Cc: Chasel Chiu <chasel.chiu@intel.com>,
Nate DeSimone <nathaniel.l.desimone@intel.com>,
Sai Chaganty <rangasai.v.chaganty@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Saloni Kasbekar <saloni.kasbekar@intel.com>,
Zachary Clark-williams <zachary.clark-williams@intel.com>
Subject: Re: [edk2-devel] [PATCH edk2-non-osi 0/1] (RFC) Drivers/Intel/IntelUndiBin: Add binaries for Intel UNDI 29.3 drivers
Date: Mon, 28 Oct 2024 13:58:09 -0600 [thread overview]
Message-ID: <cfa7a3c8-d451-465e-bf14-102f81a7882f@bsdio.com> (raw)
In-Reply-To: <18025A0F5E503E26.19860@groups.io>
I got feedback in today's CI and Tools meeting that this isn't something
we want in edk2-non-osi.
There should be a single source of the binaries, and that's Intel's
site, so please ignore this patch.
--
Rebecca
On 10/27/24 9:50 AM, Rebecca Cran wrote:
> Add binaries for the Intel UNDI UEFI drivers release 29.3.
> These were built from the sources downloaded from the "Intel® Ethernet
> Connections Boot Utility, Preboot Images, and EFI Drivers" page at
> https://www.intel.com/content/www/us/en/download/15755/intel-ethernet-connections-boot-utility-preboot-images-and-efi-drivers.html.
>
> The sources were extracted from the PREBOOT.exe file contained in the
> PREBOOT.zip download. They can be found at
> https://github.com/bexcran/IntelUndiPkg and built with the build.cmd
> script using VS2017. That repository was created based on
> https://github.com/tianocore/edk2-staging/tree/Intel_UNDI.
>
> I've CC'd several people from Intel in the hopes of getting feedback
> both about whether this is something we want to add, and whether I'm
> allowed to, since `grep -rHn CONFIDENTIAL | wc -l` shows 36 files with
> the INTEL CONFIDENTIAL header. Given Intel are publishing the sources on
> their website I suspect this is an oversight but I'd like to get
> confirmation if possible.
>
> Rebecca Cran (1):
> Drivers/Intel/IntelUndiBin: Add binaries for Intel UNDI 29.3 drivers
>
> Drivers/Intel/IntelUndiBin/GigUndiBinDebug.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/GigUndiBinNoopt.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/GigUndiBinRelease.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/I40eUndiBinDebug.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/I40eUndiBinNoopt.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/I40eUndiBinRelease.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/IceUndiBinDebug.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/IceUndiBinRelease.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/XGigUndiBinDebug.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/XGigUndiBinNoopt.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/XGigUndiBinRelease.inf | 24 ++++++++++++++++++++
> Drivers/Intel/IntelUndiBin/Debug/AARCH64/GigUndiDxe.efi | Bin 0 -> 190464 bytes
> Drivers/Intel/IntelUndiBin/Debug/AARCH64/I40eUndiDxe.efi | Bin 0 -> 131072 bytes
> Drivers/Intel/IntelUndiBin/Debug/AARCH64/IceUndiDxe.efi | Bin 0 -> 151040 bytes
> Drivers/Intel/IntelUndiBin/Debug/AARCH64/XGigUndiDxe.efi | Bin 0 -> 178176 bytes
> Drivers/Intel/IntelUndiBin/Debug/X64/GigUndiDxe.efi | Bin 0 -> 189952 bytes
> Drivers/Intel/IntelUndiBin/Debug/X64/I40eUndiDxe.efi | Bin 0 -> 137376 bytes
> Drivers/Intel/IntelUndiBin/Debug/X64/IceUndiDxe.efi | Bin 0 -> 156288 bytes
> Drivers/Intel/IntelUndiBin/Debug/X64/XGigUndiDxe.efi | Bin 0 -> 179040 bytes
> Drivers/Intel/IntelUndiBin/Noopt/AARCH64/GigUndiDxe.efi | Bin 0 -> 394752 bytes
> Drivers/Intel/IntelUndiBin/Noopt/AARCH64/I40eUndiDxe.efi | Bin 0 -> 299520 bytes
> Drivers/Intel/IntelUndiBin/Noopt/AARCH64/IceUndiDxe.efi | Bin 0 -> 493568 bytes
> Drivers/Intel/IntelUndiBin/Noopt/AARCH64/XGigUndiDxe.efi | Bin 0 -> 371712 bytes
> Drivers/Intel/IntelUndiBin/Noopt/X64/GigUndiDxe.efi | Bin 0 -> 351040 bytes
> Drivers/Intel/IntelUndiBin/Noopt/X64/I40eUndiDxe.efi | Bin 0 -> 276416 bytes
> Drivers/Intel/IntelUndiBin/Noopt/X64/IceUndiDxe.efi | Bin 0 -> 468576 bytes
> Drivers/Intel/IntelUndiBin/Noopt/X64/XGigUndiDxe.efi | Bin 0 -> 332288 bytes
> Drivers/Intel/IntelUndiBin/Release/AARCH64/GigUndiDxe.efi | Bin 0 -> 185856 bytes
> Drivers/Intel/IntelUndiBin/Release/AARCH64/I40eUndiDxe.efi | Bin 0 -> 128000 bytes
> Drivers/Intel/IntelUndiBin/Release/AARCH64/IceUndiDxe.efi | Bin 0 -> 155136 bytes
> Drivers/Intel/IntelUndiBin/Release/AARCH64/XGigUndiDxe.efi | Bin 0 -> 174080 bytes
> Drivers/Intel/IntelUndiBin/Release/X64/GigUndiDxe.efi | Bin 0 -> 181472 bytes
> Drivers/Intel/IntelUndiBin/Release/X64/I40eUndiDxe.efi | Bin 0 -> 128896 bytes
> Drivers/Intel/IntelUndiBin/Release/X64/IceUndiDxe.efi | Bin 0 -> 156000 bytes
> Drivers/Intel/IntelUndiBin/Release/X64/XGigUndiDxe.efi | Bin 0 -> 169856 bytes
> 35 files changed, 264 insertions(+)
> create mode 100644 Drivers/Intel/IntelUndiBin/GigUndiBinDebug.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/GigUndiBinNoopt.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/GigUndiBinRelease.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/I40eUndiBinDebug.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/I40eUndiBinNoopt.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/I40eUndiBinRelease.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/IceUndiBinDebug.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/IceUndiBinRelease.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/XGigUndiBinDebug.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/XGigUndiBinNoopt.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/XGigUndiBinRelease.inf
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/AARCH64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/AARCH64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/AARCH64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/AARCH64/XGigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/X64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/X64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/X64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Debug/X64/XGigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/AARCH64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/AARCH64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/AARCH64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/AARCH64/XGigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/X64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/X64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/X64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Noopt/X64/XGigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/AARCH64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/AARCH64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/AARCH64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/AARCH64/XGigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/X64/GigUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/X64/I40eUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/X64/IceUndiDxe.efi
> create mode 100644 Drivers/Intel/IntelUndiBin/Release/X64/XGigUndiDxe.efi
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120689): https://edk2.groups.io/g/devel/message/120689
Mute This Topic: https://groups.io/mt/109241480/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next parent reply other threads:[~2024-10-28 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18025A0F5E503E26.19860@groups.io>
2024-10-28 19:58 ` Rebecca Cran [this message]
2024-10-27 15:50 [edk2-devel] [PATCH edk2-non-osi 0/1] (RFC) Drivers/Intel/IntelUndiBin: Add binaries for Intel UNDI 29.3 drivers Rebecca Cran
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=cfa7a3c8-d451-465e-bf14-102f81a7882f@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