From: Dave Jones <davej@redhat.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Latest microcode data from Intel.
Date: Wed, 15 Sep 2004 16:52:15 +0100 [thread overview]
Message-ID: <20040915155215.GB24892@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0409151641430.3504-100000@einstein.homenet>
On Wed, Sep 15, 2004 at 04:43:59PM +0100, Tigran Aivazian wrote:
> The microcode driver handles the case of different types of CPUs in an SMP
> system internally. Namely, it selects the appropriate microcode data
> chunks for each CPU and then uploads them correctly to each one. Anyway,
> it only works for Intel processors, so AMD is not in the equation anyway
> (unless I discover that AMD processors support similar feature and enhance
> the driver to support it).
They do support the feature, but AMD folks have stated on this list that they
don't intend to release any updates other than through their
conventional means (Ie, BIOS updates).
There was a post just 2-3 weeks ago where someone patched microcode.c to
work on AMD64s.
Dave
next prev parent reply other threads:[~2004-09-15 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 16:32 Latest microcode data from Intel Tigran Aivazian
2004-09-09 21:10 ` DaMouse
2004-09-10 15:39 ` Bill Davidsen
2004-09-10 15:46 ` Tigran Aivazian
2004-09-10 14:54 ` Alan Cox
2004-09-10 16:04 ` Tigran Aivazian
2004-09-10 16:39 ` Chris Wright
2004-09-11 21:10 ` Tigran Aivazian
2004-09-10 16:14 ` Kurt Wall
2004-09-15 15:31 ` Bill Davidsen
2004-09-15 15:43 ` Tigran Aivazian
2004-09-15 15:52 ` Dave Jones [this message]
2004-09-15 16:09 ` Bill Davidsen
2004-09-10 15:47 ` Nathan Bryant
2004-09-10 15:02 ` Alan Cox
2004-09-10 15:53 ` Tigran Aivazian
2004-09-10 16:44 ` Anton Blanchard
2004-09-10 16:53 ` Dominik Karall
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 22:21 Chris Rankin
2004-09-10 21:07 watermodem
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=20040915155215.GB24892@redhat.com \
--to=davej@redhat.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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