Hi Giray,

UEFI SCT development had been moved into public at this point.

While we don't seem to have added helpful tags (oops - Edhaya, is that
something you can look into),
the code you're after is in https://github.com/tianocore/edk2-test/
and I think the commit you want
is 41ede93bf911a2db9e600a629f52bded82b9a802.

Best Regards,

Leif

On Wed, 28 Oct 2026 at 10:17, Yalcin, Giray via groups.io
<[email protected]> wrote:
>
> Hello,
>
> I'm working on a task that requires building UEFI SCT 2.6A from source, 
> specifically the content referenced in the official 
> UEFI2.6SCTII_Final_Release package's release note, which points to:
>
>
>
> Repository: https://github.com/UEFI/UEFI-SCT.git
>
> Tag: UEFI-2.6A-SCT-II
>
>
>
> The release note itself states this repository requires requesting access 
> through a UEFI Admin. I've confirmed that UEFI/UEFI-SCT is not among the 
> current public repositories under the UEFI GitHub org, so I'm reaching out to 
> ask:
>
> Is this repository still available, and if so, who can grant read access to 
> it?
> If it's no longer maintained separately, is the 2.6A-era source available 
> anywhere else (e.g. folded into tianocore/edk2-test under a tag I may have 
> missed, or archived elsewhere)?
> If there is a different/updated process for getting 2.6A source today, I'd 
> appreciate being pointed to it.
>
> For context: I already have the prebuilt SCT 2.6A binary package 
> (UEFISCT/IHVSCT, including AARCH64), but my assignment specifically requires 
> building from source rather than using the prebuilt binaries.
>
> Thank you for your time,
> Giray Yalcin
> HPE Compute Engineering
>
> Github.com username: giray-yalcin_hpeprod
>
>
>
>
>
> 


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#122216): https://edk2.groups.io/g/devel/message/122216
Mute This Topic: https://groups.io/mt/121974063/21656
Group Owner: [email protected]
Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to