From: "Taiidan@gmx.com" <Taiidan@gmx.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Microcode updates for "old" Intel CPU's
Date: Sun, 7 Jan 2018 15:46:52 -0500 [thread overview]
Message-ID: <de1d77f6-8d16-a696-0ebc-68c1c37e0b0e@gmx.com> (raw)
I have several sandy/ivybridge CPU's and I was wondering if anyone knows
as to if intel is releasing microcode updates for them.
It sure would be funny if intel wanted you to buy a new CPU to fix a
problem that was their fault to begin with.
next reply other threads:[~2018-01-07 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 20:46 Taiidan [this message]
2018-01-08 0:00 ` [gentoo-user] Microcode updates for "old" Intel CPU's Peter Humphrey
2018-01-08 0:55 ` R0b0t1
2018-01-09 8:43 ` Luigi Mantellini
2018-01-08 4:47 ` Adam Carter
2018-01-08 17:47 ` Corbin Bird
2018-01-09 7:56 ` Mick
2018-01-10 1:33 ` Corbin Bird
2018-01-10 1:46 ` Rich Freeman
2018-01-11 22:41 ` Mick
2018-01-11 23:02 ` Rich Freeman
2018-01-12 16:23 ` Corbin Bird
2018-01-12 17:21 ` Taiidan
[not found] ` <1542759.NuuG9cTaQ6@dell_xps>
2018-01-13 18:14 ` Taiidan
2018-01-12 17:47 ` Rich Freeman
2018-01-12 18:42 ` Mick
2018-01-12 19:06 ` Rich Freeman
2018-01-12 20:32 ` Taiidan
2018-01-12 19:58 ` Corbin Bird
2018-01-12 20:18 ` Rich Freeman
2018-01-13 0:03 ` Adam Carter
2018-01-13 0:06 ` Adam Carter
2018-01-12 16:23 ` Daniel Frey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de1d77f6-8d16-a696-0ebc-68c1c37e0b0e@gmx.com \
--to=taiidan@gmx.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox