From: Andrew Morton <akpm@linux-foundation.org>
To: Valdis.Kletnieks@vt.edu
Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
Date: Wed, 2 Jul 2008 18:43:15 -0700 [thread overview]
Message-ID: <20080702184315.f659ec92.akpm@linux-foundation.org> (raw)
In-Reply-To: <4534.1215048758@turing-police.cc.vt.edu>
On Wed, 02 Jul 2008 21:32:38 -0400 Valdis.Kletnieks@vt.edu wrote:
> I built the -rc8-mmotd kernel, and built it with 'CONFIG_FIRMWARE_IN_KERNEL=n'.
> Lo and behold, the microcode.ko was now doing a request_firmware for
> 'intel-ucode/06-0f-06' (which makes sense, the Core2 Duo in this laptop is
> family 6, model 15, stepping 6). However, what I had in /lib/firmware was
> the Intel-distributed 'microcode.dat' with updates for all the CPUs (which
> used to work in times past).
>
> What's the magic incantation to take the microcode.dat and create something
> that the firmware driver is willing to use, or is this all borked up and
> I need to do a major rethink or fix my config?
>
> Another minor annoyance - the tg3 driver, when builtin to the kernel, wouldn't
> load the microcode in this config. It complained it couldn't get 'tigon/tg3_tos.bin',
> but that's almost certainly an issue with Fedora's 'nash' firmware support and/or
> my understanding of it - I got *that* part working by dropping the file into
> /lib/firmware/tigon and building the driver as a module. Fortunately, I don't
> need the tg3 driver to boot far enough to get a full udev running.
>
(cc dwmw2)
next prev parent reply other threads:[~2008-07-03 7:01 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 [this message]
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
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=20080702184315.f659ec92.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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