TALOS II's coreboot's buildgcc : change IASL_ARCHIVE link to point to intel, same hash

[tlaurion]

Similar to #366 but applied to Talos II release 0.7.
Point release needed : 0.7.1

Note that Heads doesn't point to the coreboot hash as it was on release.

---

suggested workflow for point release:

• Merge under dasharo/coreboot fork Dasharo:raptor-cs_talos-2/rel_v0.7.1
• Have commit updated under https://github.com/osresearch/heads/blob/02c3a1f9ee270403a962fd826ade28d642a232fb/modules/coreboot#L47 to match coreboot commit under Heads PR
  • Have that PR remove current mitigation patches, present under https://github.com/osresearch/heads/tree/master/patches/coreboot-talos_2 and applied on top of coreboot-git directory as per https://github.com/osresearch/heads/blob/02c3a1f9ee270403a962fd826ade28d642a232fb/modules/coreboot#L46
• Have PR merged under Heads (tested for no regression on Heads side)
• Do Dasharo release, pointing to good Heads used coreboot hash, with Heads version matching the commit ID pointing to good coreboot fork under https://docs.dasharo.com/variants/talos_2/releases/ notes

Doing so, SBOM would be valid. Otherwise, BOM is invalid.
Heads coreboot's hash won't match what is in your release. (as of now for 0.7)

[miczyg1]

Why don't we use the same lin kas here? #366

IASL_VERSION is 20220331 here as well @tlaurion

[tlaurion]

@miczyg1 as you see fit. Same will apply to kgpe-d6 dasharo fork and all other forks. This was just a guideline to be followed, meanwhile staging patches missing newer commit under Heads lies into forks staging dirs.