From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [edk2-platforms] [PATCH V1 5/5] KabylakeOpenBoardPkg/GalagoPro3: Enable HDMI DDC Debug Port To: Nate DeSimone ,devel@edk2.groups.io From: "Benjamin Doron" X-Originating-Location: Richmond Hill, Ontario, CA (24.52.200.135) X-Originating-Platform: Linux Firefox 101 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sun, 19 Jun 2022 13:06:31 -0700 References: <20220618040550.8467-6-nathaniel.l.desimone@intel.com> In-Reply-To: <20220618040550.8467-6-nathaniel.l.desimone@intel.com> Message-ID: <7740.1655669191017394824@groups.io> Content-Type: multipart/alternative; boundary="Lh2AFNnW5qlHmQ6tVsOG" --Lh2AFNnW5qlHmQ6tVsOG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Nate, It looks like you have the SerialPortLib linked into the wrong RSC module i= n the SMM instance. It should be linked into the handler, as it is for the = other phases here. You probably just copied the wrong module name, but this= is why logging isn't working. In general, I don't know why PiSmmCpuDxeSmm ever gets special treatment: I'= ve been using RSC to handle writing debug logs for all phases from PEI core= onwards without issue. Only SEC core and the RSC handlers are getting the = NULL instance. Regards, Benjamin --Lh2AFNnW5qlHmQ6tVsOG Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Nate,
It looks like you have the SerialPortLib linked into the wron= g RSC module in the SMM instance. It should be linked into the handler, as = it is for the other phases here. You probably just copied the wrong module = name, but this is why logging isn't working.

In general, I don't= know why PiSmmCpuDxeSmm ever gets special treatment: I've been using RSC t= o handle writing debug logs for all phases from PEI core onwards without is= sue. Only SEC core and the RSC handlers are getting the NULL instance.

Regards,
Benjamin --Lh2AFNnW5qlHmQ6tVsOG--