From: Matt Reuther <mreuther@umich.edu>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Compile Error on 2.6.17-mm6
Date: Sun, 9 Jul 2006 03:20:15 -0400 [thread overview]
Message-ID: <200607090320.15632.mreuther@umich.edu> (raw)
In-Reply-To: <20060708213734.a204a044.rdunlap@xenotime.net>
On Sunday 09 July 2006 12:37 am, Randy.Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> MICROCODE needs FW_LOADER functions.
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> ---
> arch/i386/Kconfig | 1 +
> arch/x86_64/Kconfig | 1 +
> 2 files changed, 2 insertions(+)
>
> --- linux-2617-mm6.orig/arch/x86_64/Kconfig
> +++ linux-2617-mm6/arch/x86_64/Kconfig
> @@ -159,6 +159,7 @@ config X86_GOOD_APIC
>
> config MICROCODE
> tristate "/dev/cpu/microcode - Intel CPU microcode support"
> + depends on FW_LOADER
> ---help---
> If you say Y here the 'File systems' section, you will be
> able to update the microcode on Intel processors. You will
> --- linux-2617-mm6.orig/arch/i386/Kconfig
> +++ linux-2617-mm6/arch/i386/Kconfig
> @@ -399,6 +399,7 @@ config X86_REBOOTFIXUPS
>
> config MICROCODE
> tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
> + depends on FW_LOADER
> ---help---
> If you say Y here and also to "/dev file system support" in the
> 'File systems' section, you will be able to update the microcode on
This fixes the error. Thanks for your help!
Matt
next prev parent reply other threads:[~2006-07-09 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 2:22 Matt Reuther
2006-07-09 0:43 ` Andrew Morton
2006-07-09 3:34 ` Randy.Dunlap
2006-07-09 3:44 ` Andrew Morton
2006-07-09 4:37 ` Randy.Dunlap
2006-07-09 4:58 ` Andrew Morton
2006-07-09 7:20 ` Matt Reuther [this message]
2006-07-09 8:25 ` Adrian Bunk
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=200607090320.15632.mreuther@umich.edu \
--to=mreuther@umich.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®