Sounds good to me, thanks!
Best regards,
Marvin
> On 13. Feb 2023, at 23:07, Ard Biesheuvel wrote:
>
> On Mon, 13 Feb 2023 at 22:32, Marvin Häuser wrote:
>>
>> Without wanting to blow up your RFC with another one - I discussed this with
>> various people, including Bret when he was still at
On Mon, 13 Feb 2023 at 22:32, Marvin Häuser wrote:
>
> Without wanting to blow up your RFC with another one - I discussed this with
> various people, including Bret when he was still at Project Mu, and there was
> a consensus among them that integrating the whole CPU arch code right into
> DxeC
Without wanting to blow up your RFC with another one - I discussed this with
various people, including Bret when he was still at Project Mu, and there was a
consensus among them that integrating the whole CPU arch code right into
DxeCore would be a good idea. This would especially remove the hac
Store the address of the SetMemoryAttributes() member of the CPU arch
protocol in a global variable, and invoke it via this variable. This
by itself should have not result in functional changes, but it permits
platforms to provide an preliminary implementation of this member at
link time, allowing
