| 1 |
On Thu, Apr 12, 2018 at 9:20 PM, Taiidan@×××.com <Taiidan@×××.com> wrote: |
| 2 |
> When is gentoo going to receive these? |
| 3 |
> |
| 4 |
|
| 5 |
Has AMD actually released anything publicly? I find AMD's microcode |
| 6 |
updates to be horribly documented in general, unless there is some |
| 7 |
website somewhere published by AMD that somebody could be helpful |
| 8 |
enough to point out... |
| 9 |
|
| 10 |
Typically these work their way into linux-firmware, somehow, usually |
| 11 |
without any indication as to what they actually do. Back when Spectre |
| 12 |
first was discovered there was a microcode update being circulated |
| 13 |
that many thought addressed Spectre but my understanding is that it |
| 14 |
turned out to have nothing to do with it. Not that you would |
| 15 |
necessarily know one way or another as it is just a binary blob devoid |
| 16 |
of any kind of release notes. |
| 17 |
|
| 18 |
I've always been an AMD fan but they'd do their customers a great |
| 19 |
service if they just posted a website with links to various versions |
| 20 |
of their microcode and even a sentence or two describing why each was |
| 21 |
released. |
| 22 |
|
| 23 |
All that said, once you do get updated microcode it can be loaded |
| 24 |
following some instructions on the wiki (easiest way is to embed the |
| 25 |
microcode in the kernel and there might be a kernel option you need to |
| 26 |
toggle). |
| 27 |
|
| 28 |
Looking at the linux-firmware upstream git I don't see any recent |
| 29 |
AMD-related commits there. |
| 30 |
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ |
| 31 |
|
| 32 |
In any case, if somebody spots a blob from someplace reasonably |
| 33 |
credible I'm sure the linux-firmware maintainers wouldn't object to |
| 34 |
filing a bug... |
| 35 |
|
| 36 |
-- |
| 37 |
Rich |
Archives