From: Arjan van de Ven <arjan@infradead.org>
To: "Giacomo A. Catenazzi" <cate@debian.org>
Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
"Selbak, Rolla N" <rolla.n.selbak@intel.com>,
Shaohua Li <shaohua.li@intel.com>
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
Date: Thu, 3 Jul 2008 06:56:30 -0700 [thread overview]
Message-ID: <20080703065630.2aefc930@infradead.org> (raw)
In-Reply-To: <486C9AD2.6020604@debian.org>
On Thu, 03 Jul 2008 11:24:34 +0200
"Giacomo A. Catenazzi" <cate@debian.org> wrote:
> There are two format of Intel CPU microcode and two methods to load
> it.
> - old: the microcodes are in a big file, which include multiple
> microcodes (for multiple CPU). The driver require a char device
> and a user space loader ("microcode_ctl")
> - new: one microcode per file, using the 'request_firmware'
> infrastructure. No user space support needed.
>
> Actually Intel provides only the old methods.
> There was talks with Arjan and Intel about the distribution format
> for the new methods. But I don't have any new.
> I think that when the new format is fully specified (directory
> structure, tar, gzip,...) Intel will distribute the microcodes
> in the new form.
we hope to switch to the new form but there's the small case of
"installed base" using ancient kernels, and it's kind of not nice to
have to release 2 sets. At some point we will switch over though.
next prev parent reply other threads:[~2008-07-03 13:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 1:32 Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware Valdis.Kletnieks
2008-07-03 1:43 ` Andrew Morton
2008-07-03 6:17 ` Tigran Aivazian
2008-07-03 6:35 ` Valdis.Kletnieks
2008-07-03 6:44 ` Tigran Aivazian
2008-07-03 9:23 ` David Woodhouse
2008-07-03 10:17 ` Valdis.Kletnieks
2008-07-03 10:30 ` David Woodhouse
2008-07-03 11:34 ` Valdis.Kletnieks
2008-07-03 12:21 ` David Woodhouse
2008-07-03 12:41 ` Kay Sievers
2008-07-03 12:45 ` David Woodhouse
2008-07-03 13:03 ` Kay Sievers
2008-07-03 13:26 ` David Woodhouse
2008-07-03 13:54 ` Valdis.Kletnieks
2008-07-03 15:23 ` David Woodhouse
2008-07-03 13:48 ` Valdis.Kletnieks
2008-07-03 10:22 ` Kay Sievers
2008-07-03 10:42 ` David Woodhouse
2008-07-03 11:32 ` Kay Sievers
2008-07-03 9:24 ` Giacomo A. Catenazzi
2008-07-03 13:56 ` Arjan van de Ven [this message]
2008-07-03 15:54 ` David Woodhouse
2008-07-03 16:22 ` Giacomo A. Catenazzi
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=20080703065630.2aefc930@infradead.org \
--to=arjan@infradead.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=cate@debian.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rolla.n.selbak@intel.com \
--cc=shaohua.li@intel.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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