public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Subject: [edk2-devel] How to report bugs in the Intel GigUndiDxe driver?
Date: Tue, 15 Aug 2023 21:40:34 -0600	[thread overview]
Message-ID: <ae558c3e-cc0b-eed2-66ef-dba9c4f48466@bsdio.com> (raw)

Intel has been releasing the EDK2/UEFI source code for their network 
drivers 
(https://www.intel.com/content/www/us/en/download/15755/intel-ethernet-connections-boot-utility-preboot-images-and-efi-drivers.html) 
but I've found a few problems with it. The first issue I ran into is 
that GigUndiDxe.inf includes StdLibC which obviously breaks the build.

This evening I also found a problem with a debug print which causes a crash:

DEBUGPRINT (HII, ("Package list languages - %a\n"));


Less important, but slightly irritating, the documentation files such as 
build_instruction.txt are in UTF-16 format.


I was wondering if there's any way to send feedback to the team 
responsible for the driver(s) without going through the official Intel 
Support process?


Once I have it working, if there's interest I was thinking about having 
the code added to edk2-non-osi under Drivers/Intel/IntelUndiPkg. I don't 
know if that's something that would be useful?


-- 

Rebecca Cran



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107785): https://edk2.groups.io/g/devel/message/107785
Mute This Topic: https://groups.io/mt/100773221/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



             reply	other threads:[~2023-08-16  3:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  3:40 Rebecca Cran [this message]
2023-08-16 18:08 ` [edk2-devel] How to report bugs in the Intel GigUndiDxe driver? Ard Biesheuvel

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=ae558c3e-cc0b-eed2-66ef-dba9c4f48466@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