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 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#94797): https://edk2.groups.io/g/devel/message/94797 Mute This Topic: https://groups.io/mt/90308335/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
