Hi, > Because the total patch-sets for TDVF upstreaming is too big and there are 2 > configurations. > So we split the upstreaming into below waves. > Config-A Config-B Phase > Wave-1 Y Y ResetVector > Wave-2 Y N SEC/PEI > Wave-3 Y N DXE > Wave-4 N Y SEC (PEI is > skipped) > Wave-5 N Y DXE > > So this patch-set is wave-2 and for Config-A (SEC/PEI).
Thanks (please add that info to the cover letter in the future). > > Apparently some of the additional features supported by config-b are either > > more difficult or impossible to implement in config-a. > > Is that correct? Is that explained in more detail somewhere? > It's correct. Some additional features are not supported in Config-A. For > example the TD > RTMR based measured boot. Why is TD RTMR based measured boot not supported in Config-A? I'm trying to understand why we need Config-B. Having two variants with completely different initialization code paths (with/without PEI) doesn't look like a good plan to me. I'd rather support everything in Config-A if possible. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#80051): https://edk2.groups.io/g/devel/message/80051 Mute This Topic: https://groups.io/mt/84837888/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
