From: "Laszlo Ersek" <lersek@redhat.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: "Ramesh R." <rameshr@ami.com>,
Sivaraman Nainar <sivaramann@ami.com>,
manickavasakam karpagavinayagam <manickavasakamk@ami.com>
Subject: Intel NUC platform firmware -- no serial I/O support?
Date: Thu, 7 Apr 2022 09:46:12 +0200 [thread overview]
Message-ID: <4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.com> (raw)
Hi List,
my toolbox has been extended with an Intel NUC, the base kit model being
NUC8i3PNH. The NUC has a serial port connector on the back, and indeed
Serial I/O works fine once an OS starts.
However, the UEFI platform firmware seems to have no support for Serial
I/O. I've built a fresh UEFI Shell binary from edk2 master and poked
around in the protocol database, with "drivers" and "dh". The necessary
drivers seem to be included, however they do not appear to bind the
hardware that's inside the chassis. ("connect -r" makes no difference in
this regard, so it's not just BDS policy.)
Interestingly, the related drivers are all called "AMI ...", which I
find somewhat strange on an Intel-branded NUC. I don't know whom I
should be addressing with my question in the first place. Just to be
sure, I'm CC'ing a bunch of randomly picked @ami.com email addresses
from my edk2-devel list archive.
I can provide more details if needed, but first I'd like to ask if *any*
firmware update exists for this kit -- NUC8i3PNH -- where the platform
firmware can drive the serial port. My goal is (of course) completely
headless operation of the NUC; ideally, that would cover the UEFI
console too.
Right now, I need to connect an HDMI monitor and a USB keyboard+mouse to
the NUC just to get into the Setup UI / UEFI Shell.
Thanks!
Laszlo
next reply other threads:[~2022-04-07 7:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:46 Laszlo Ersek [this message]
2022-04-07 8:00 ` [edk2-devel] Intel NUC platform firmware -- no serial I/O support? Gerd Hoffmann
2022-04-07 10:49 ` Laszlo Ersek
2022-04-07 12:50 ` Gerd Hoffmann
2022-04-07 14:12 ` Laszlo Ersek
2022-04-07 17:04 ` manickavasakam karpagavinayagam
2022-04-08 9:19 ` Laszlo Ersek
2022-04-12 18:40 ` manickavasakam karpagavinayagam
2022-04-13 6:06 ` Laszlo Ersek
2022-04-08 9:48 ` Gerd Hoffmann
2022-04-08 11:01 ` Laszlo Ersek
2022-10-06 15:07 ` Laszlo Ersek
2022-04-07 22:16 ` Nate DeSimone
2022-04-08 9:32 ` Laszlo Ersek
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=4c8d982a-97b0-654c-c6db-9a55b95330b5@redhat.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