From: "Ashish Singhal" <ashishsingha@nvidia.com>
To: <devel@edk2.groups.io>, <michael.d.kinney@intel.com>,
<gaoliming@byosoft.com.cn>, <zhiguang.liu@intel.com>
Cc: Ashish Singhal <ashishsingha@nvidia.com>
Subject: [PATCH 0/1] Add NVIDIA 16550 UART ACPI Subtype
Date: Tue, 18 May 2021 12:37:38 -0600 [thread overview]
Message-ID: <cover.1621362650.git.ashishsingha@nvidia.com> (raw)
This patch adds macro for NVIDIA 16550 UART subtype for ACPI
tables as documented by Microsoft.
https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/acpi-debug-port-table
Ashish Singhal (1):
MdePkg: Update DBG2 and SPCR header with NVIDIA 16550 Subtype
MdePkg/Include/IndustryStandard/DebugPort2Table.h | 1 +
.../IndustryStandard/SerialPortConsoleRedirectionTable.h | 5 +++++
2 files changed, 6 insertions(+)
--
2.17.1
next reply other threads:[~2021-05-18 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 18:37 Ashish Singhal [this message]
2021-05-18 18:37 ` [PATCH 1/1] MdePkg: Update DBG2 and SPCR header with NVIDIA 16550 Subtype Ashish Singhal
2021-05-18 21:14 ` [edk2-devel] " Samer El-Haj-Mahmoud
2021-05-20 20:32 ` Ashish Singhal
2021-05-21 5:20 ` 回复: " gaoliming
2021-05-21 6:08 ` Sunny Wang
[not found] ` <1680FD5B20378614.12041@groups.io>
2021-05-21 5:27 ` 回复: " gaoliming
[not found] ` <1680FDC38B67BCC1.12041@groups.io>
2021-06-02 5:56 ` gaoliming
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=cover.1621362650.git.ashishsingha@nvidia.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