-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to get a redistributable copy of "Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop Processors"? #81
Comments
Hi folks. Thanks for bringing this to our attention. We're looking at the best way to handle this usage to indicate when an MCU doesn't add anything over the previous MCU from the OS loading standpoint. For now, here is the MCU file (Linux/pdb format). I presume that this format works for your use since you have been relying on this repository. |
@whpenner Thank you! |
Many thanks, @whpenner! |
The microcode and the redistribution license were published in a GitHub issue [1] from that repository. It might be added to the repository at some later point. The signature says: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: Ic274af7d862cf1c2fe0aaf8b9c228618fb970fad Signed-off-by: Felix Singer <[email protected]>
This updated microcode fixes the recent voltage issues on the Raptor Lake S platform. Intel provided this specific microcode just as an attachment [1]. Thus, we've uploaded it to our own blobs repository, which is why the path is changed. Microcode signature: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: I6d01e38476b0d3dc5281ea1d85bac87043d122dd Signed-off-by: Felix Singer <[email protected]> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84132 Reviewed-by: Nico Huber <[email protected]> Tested-by: build bot (Jenkins) <[email protected]>
This updated microcode fixes the recent voltage issues on the Raptor Lake S platform. Intel provided this specific microcode just as an attachment [1]. Thus, we've uploaded it to our own blobs repository, which is why the path is changed. Microcode signature: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: I6d01e38476b0d3dc5281ea1d85bac87043d122dd Signed-off-by: Felix Singer <[email protected]> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84132 Reviewed-by: Nico Huber <[email protected]> Tested-by: build bot (Jenkins) <[email protected]>
This updated microcode fixes the recent voltage issues on the Raptor Lake S platform. Intel provided this specific microcode just as an attachment [1]. Thus, we've uploaded it to our own blobs repository, which is why the path is changed. Microcode signature: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: I6d01e38476b0d3dc5281ea1d85bac87043d122dd Signed-off-by: Felix Singer <[email protected]> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84132 Reviewed-by: Nico Huber <[email protected]> Tested-by: build bot (Jenkins) <[email protected]>
Hey @whpenner, since a new microcode to address Vmin Shift Instability issue more fully has been released to manufacturers by Intel, any chance of publishing 0x12B here as well? |
This updated microcode fixes the recent voltage issues on the Raptor Lake S platform. Intel provided this specific microcode just as an attachment [1]. Thus, we've uploaded it to our own blobs repository, which is why the path is changed. Microcode signature: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: I6d01e38476b0d3dc5281ea1d85bac87043d122dd Signed-off-by: Felix Singer <[email protected]> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84132 Reviewed-by: Nico Huber <[email protected]> Tested-by: build bot (Jenkins) <[email protected]>
This updated microcode fixes the recent voltage issues on the Raptor Lake S platform. Intel provided this specific microcode just as an attachment [1]. Thus, we've uploaded it to our own blobs repository, which is why the path is changed. Microcode signature: sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129 [1] intel/Intel-Linux-Processor-Microcode-Data-Files#81 Change-Id: I6d01e38476b0d3dc5281ea1d85bac87043d122dd Signed-off-by: Felix Singer <[email protected]> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84132 Reviewed-by: Nico Huber <[email protected]> Tested-by: build bot (Jenkins) <[email protected]>
In #78 it was argued that the elevated-voltage related update won't be distributed via this repository to avoid confusion (as it can't be applied from the OS). However, independent manufacturers and firmware vendors rely on redistributable binaries (as they are licensed in this repository) when they don't work very close to Intel. Especially when open-source firmware is involved that sometimes even the customers compile themselves, the chain becomes too long to sign an NDA for every single case.
How can we get redistributable binaries for such not-OS-applicable updates into the ecosystem?
The text was updated successfully, but these errors were encountered: