From: Dominik Karall <dominik.karall@gmx.net>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Latest microcode data from Intel.
Date: Fri, 10 Sep 2004 18:53:48 +0200 [thread overview]
Message-ID: <200409101853.48850.dominik.karall@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0409091726010.2713-100000@einstein.homenet>
On Thursday 09 September 2004 18:32, Tigran Aivazian wrote:
> Hello,
>
> I have received and tested the latest microcode data file from Intel, The
> file is dated 2nd September 2004. You can download it both as standalone
> (bzip2-ed) text file and bundled with microcode_ctl utility from the
> Download section of the website:
>
> http://urbanmyth.org/microcode/
>
> Please let me know if you find any problems with this data file or with
> the Linux microcode driver. Thank you.
>
> Kind regards
> Tigran
i read about intel microcode upgrade before, but i never tried it. so my
question is, are there any reasons why somebody should upgrade his microcode?
i know that intel does not hand out a changelog, but maybe anybody knows more
about it. thx in advance!
best regards,
dominik
next prev parent reply other threads:[~2004-09-10 16:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=200409101853.48850.dominik.karall@gmx.net \
--to=dominik.karall@gmx.net \
--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
all inboxes | Powered by JetHome®