For the purpose of UEFI debug prints enablement in DXE phase,
Serial driver should load earlier. Separate .inf file is created
in order to make minimal changes to current implementation.
Signed-off-by: Alan Borzeszkowski
---
.../PciSioSerialDxe/PciSioSerialDxeEarly.inf | 80 +++
On Intel platforms, we use LPSS UART for debug prints in DXE phase. Current
implementation involves using custom driver.
In order to reduce code maintenance cost and flash usage, we want to switch to
EDK2 Serial driver.
To achieve that, we need to load Serial driver shortly after DXE Core is
Could you elaborate on that?
Also, could you please explain why DXE drivers cannot use Driver Binding?
Regards,
Alan
-Original Message-
From: Kinney, Michael D
Sent: Tuesday, February 20, 2024 6:12 PM
To: devel@edk2.groups.io; Borzeszkowski, Alan
Cc: Albecki, Mateusz ; Gao, Zhicha
For the purpose of UEFI debug prints enablement in early DXE,
Serial driver should load earlier. To comply with EDK2 specification
and maximize code reuse, new driver entrypoint was created
and separate .inf file was added.
Cc: Zhichao Gao
Cc: Ray Ni
Cc: Michael D Kinney
Signed-off-by: Alan
On Intel platforms, we use LPSS UART for debug prints in DXE phase. Current
implementation involves using custom driver.
In order to reduce code maintenance cost and flash usage, we want to switch to
EDK2 Serial driver.
Given that PciSioSerialDxe is a UEFI driver and for purposes of loading this
Sorry, I did not provide full picture. After this discussion on devel I've
linked, I spoke to Michael what changes would be in compliance with EDK2 driver
model guidelines. An agreement was reached: Root Bridge driver that implements
SIO Protocol and Serial I/O driver (with new entrypoint) that
We have considered that; however, we aim to avoid maintaining our own
implementation of functions that communicate with UART.
Please see discussion over previous approach:
https://edk2.groups.io/g/devel/topic/104469297#115731
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages
