From: "Laszlo Ersek" <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, devel@edk2.groups.io
Cc: "Ramesh R." <rameshr@ami.com>,
Sivaraman Nainar <sivaramann@ami.com>,
manickavasakam karpagavinayagam <manickavasakamk@ami.com>
Subject: Re: [edk2-devel] Intel NUC platform firmware -- no serial I/O support?
Date: Thu, 6 Oct 2022 17:07:18 +0200 [thread overview]
Message-ID: <df2eeefc-e17a-954b-2495-2c4f1ea35964@redhat.com> (raw)
In-Reply-To: <d57aaf9c-4a6c-e41b-871e-3c7c79065753@redhat.com>
On 04/07/22 12:49, Laszlo Ersek wrote:
> On the NUC, this whole child controller chain, and protocol stack,
> breaks down because there is no SerialIo protocol interface in the
> protocol db. The following command returns nothing, even after "connect
> -r":
>
>> Shell> dh -d -v -p SerialIo
>
> (On OVMF, the command returns handle BE, see above.)
It's hard to understand the "secret decisions" about physical platform
firmware. I'm working with a new NUC now, and this one does provide a
functional SerialIo protocol implementation out of the box (with the
"AMI Serial I/O Driver" actually doing its job, unlike in the previous
NUC). However, TerminalDxe is *still* not included in the platform
firmware. Unfathomable. (Well, "TerminalSrc", aka "AMI Terminal Driver"
is included, but like on the earlier NUC, it seems to be doing nothing;
it doesn't bind SerialIo.)
Laszlo
next prev parent reply other threads:[~2022-10-06 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:46 Intel NUC platform firmware -- no serial I/O support? Laszlo Ersek
2022-04-07 8:00 ` [edk2-devel] " 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 [this message]
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=df2eeefc-e17a-954b-2495-2c4f1ea35964@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