From: Arjan van de Ven <arjan@linux.intel.com>
To: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux* Processor Microcode Data File
Date: Mon, 9 Mar 2009 07:27:25 -0700 [thread overview]
Message-ID: <20090309072725.45a895f1@linux.intel.com> (raw)
In-Reply-To: <2d05c4580903090243k6cf73ee9ubb6c4fccf0f07a2f@mail.gmail.com>
On Mon, 9 Mar 2009 10:43:57 +0100
Dragoslav Zaric <dragoslav.zaric.kd@gmail.com> wrote:
> Hello,
>
> I was browsing Intel web site for my processor docs and I bumped
> on download link "Linux* Processor Microcode Data File" and it says
> there:
>
> "The microcode data file contains the latest microcode definitions for
> all Intel processors.
> Intel releases microcode updates to correct processor behavior as
> documented in the respective
> processor specification updates. While the regular approach to getting
> this microcode update is via
> a BIOS upgrade, Intel realizes that this can be an administrative
> hassle. The Linux Operating System
> and VMware ESX products have a mechanism to update the microcode after
> booting. For example,
> this file will be used by the operating system mechanism if the file
> is placed in the /etc/firmware
> directory of the Linux system."
>
> So, does new kernel versions just copy this microcode update file in
> /etc/firmware folder
yup just place it there.... and it'll get picked up.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2009-03-09 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 9:43 Linux* Processor Microcode Data File Dragoslav Zaric
2009-03-09 10:00 ` Jike Song
2009-03-09 10:30 ` Andreas Herrmann
2009-03-09 14:16 ` Sitsofe Wheeler
2009-03-09 15:11 ` Arjan van de Ven
2009-03-09 15:34 ` Sitsofe Wheeler
2009-03-09 15:58 ` Gene Heskett
2009-03-09 16:24 ` Sitsofe Wheeler
2009-03-09 17:03 ` Gene Heskett
2009-03-09 17:57 ` Andreas Herrmann
2009-03-09 16:53 ` Arjan van de Ven
2009-03-12 10:03 ` Giacomo A. Catenazzi
2009-03-12 14:07 ` Arjan van de Ven
2009-03-13 8:37 ` Giacomo A. Catenazzi
[not found] ` <2d05c4580903130142o2e5ebbcfw1e35eb52ea48e4b1@mail.gmail.com>
2009-03-13 8:44 ` Dragoslav Zaric
2009-03-13 14:55 ` Gene Heskett
2009-03-12 14:53 ` Dragoslav Zaric
2009-03-09 14:27 ` Arjan van de Ven [this message]
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=20090309072725.45a895f1@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=dragoslav.zaric.kd@gmail.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.