On 01/08/2018 05:44 PM, Bruce Dubbs wrote:
DJ Lucas wrote:
I might be confused, but I thought microcode updates on consumer
processors is handled by BIOS update from the motherboard
manufacturer, the AGESA part of the BIOS version, currently 1.0.0.7.
I'm not sure if we'll see a late-load
On 01/08/2018 03:12 PM, Michael Shell wrote:
On Sun, 7 Jan 2018 16:47:00 -0600
DJ Lucas wrote:
I might be confused, but I thought microcode updates on consumer
processors is handled by BIOS update from the motherboard manufacturer,
the AGESA part of the BIOS version,
DJ Lucas wrote:
I might be confused, but I thought microcode updates on consumer
processors is handled by BIOS update from the motherboard manufacturer,
the AGESA part of the BIOS version, currently 1.0.0.7. I'm not sure if
we'll see a late-load .bin for the consumer processors. If anybody
On Sun, 7 Jan 2018 16:47:00 -0600
DJ Lucas wrote:
> I might be confused, but I thought microcode updates on consumer
> processors is handled by BIOS update from the motherboard manufacturer,
> the AGESA part of the BIOS version, currently 1.0.0.7. I'm not sure if
> we'll
On Sun, Jan 07, 2018 at 04:47:00PM -0600, DJ Lucas wrote:
>
>
> I might be confused, but I thought microcode updates on consumer processors
> is handled by BIOS update from the motherboard manufacturer, the AGESA part
> of the BIOS version, currently 1.0.0.7. I'm not sure if we'll see a
>
On 01/07/2018 04:11 PM, Ken Moffat wrote:
On Fri, Jan 05, 2018 at 08:43:11PM -0500, Michael Shell wrote:
On Fri, 5 Jan 2018 17:26:13 +
Ken Moffat wrote:
Does anybody have a link for (any) updated AMD firmware? Ryzen is
model 17h, AFAICS linux firmware has
On Fri, 5 Jan 2018 17:26:13 +
Ken Moffat wrote:
> Does anybody have a link for (any) updated AMD firmware? Ryzen is
> model 17h, AFAICS linux firmware has nothing for that, and the
> firmware for earlier models has not been updated in a long time.
I also sure
On Fri, Jan 05, 2018 at 02:58:57AM -0500, Michael Shell wrote:
>
> Most interesting, but also scary. Here's my own summary take on the info
> which I found at:
>
[ snipping - people can, and should, follow the links in your original
post, but I've got a question on one item ]
>
> There is,
On Thu, 4 Jan 2018 20:16:18 +
Ken Moffat wrote:
> There are two vulnerabilities, with the shiny names of Meltdown and
> Spectre. Both refer to ways of userspace finding where the kernel
> has been mapped, to try to do harm. Page Table Isolation addresses
> the first