From: "Chris Rankin" <rankincj@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: RE: Latest microcode data from Intel.
Date: Thu, 9 Sep 2004 23:21:45 +0100 (BST) [thread overview]
Message-ID: <20040909222145.42540.qmail@web52902.mail.yahoo.com> (raw)
> I have received and tested the latest microcode data
> file from Intel, The file is dated 2nd September
> 2004.
Aha! And this microcode file actually contains data
for my dual P4 Xeons (HT):
IA-32 Microcode Update Driver: v1.14 <tigran@xxxx>
microcode: CPU2 updated from revision 0x18 to 0x22,
date = 03242004
microcode: CPU1 updated from revision 0x18 to 0x22,
date = 03242004
microcode: CPU0 updated from revision 0x18 to 0x22,
date = 03242004
microcode: CPU3 updated from revision 0x18 to 0x22,
date = 03242004
The July 27th offering didn't contain anything for
these CPUs at all. In fact, the July file was
suspiciously smaller than the one from 16th March.
Chris
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
next reply other threads:[~2004-09-09 22:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 22:21 Chris Rankin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 21:07 Latest microcode data from Intel watermodem
2004-09-09 16:32 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
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
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=20040909222145.42540.qmail@web52902.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.