From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] How to add a DXE driver to an OVMF image? To: d.meneses@softi9.pt,devel@edk2.groups.io From: d.meneses@softi9.pt X-Originating-Location: Madrid, ES (45.152.183.60) X-Originating-Platform: Linux Chrome 106 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 04 Nov 2022 06:20:54 -0700 References: <22885.1667513571456708695@groups.io> In-Reply-To: <22885.1667513571456708695@groups.io> Message-ID: <17126.1667568054194961949@groups.io> Content-Type: multipart/alternative; boundary="SCiQaDybSvRHePgdNCPZ" --SCiQaDybSvRHePgdNCPZ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Using *DebugLib* instead to print a message, I was able to confirm that my = driver is now running properly: *cat debug.log | grep Hello* This works both when adding it in the OVMF build and also when inserted by = UEFITool. The drivers is not being=C2=A0listed by the EFI Shell *drivers* command. This is expected to me as Dxe Drivers are unloaded after they return. Nonetheless, the same is happening when I package it as a *DXE_RUNTIME_DRIV= ER*. What is it that I'm missing? Thank you for your attention, Diogo --SCiQaDybSvRHePgdNCPZ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Using DebugLib instead to print a message, I was able= to confirm that my driver is now running properly:
cat debug.log | grep Hello
This works both when adding it in the OVMF build and also when inserted by = UEFITool.

The drivers is not being listed by the EFI Shell&= nbsp;drivers command.
This is expected to me as Dxe D= rivers are unloaded after they return.
Nonetheless, the same is happen= ing when I package it as a DXE_RUNTIME_DRIVER.
What i= s it that I'm missing?

Thank you for your attention,
Diogo --SCiQaDybSvRHePgdNCPZ--