From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: mreuther@umich.edu, linux-kernel@vger.kernel.org
Subject: Re: Compile Error on 2.6.17-mm6
Date: Sat, 8 Jul 2006 20:44:48 -0700 [thread overview]
Message-ID: <20060708204448.6914aaf9.akpm@osdl.org> (raw)
In-Reply-To: <20060708203424.281400d2.rdunlap@xenotime.net>
On Sat, 8 Jul 2006 20:34:24 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> On Sat, 8 Jul 2006 17:43:47 -0700 Andrew Morton wrote:
>
> > On Fri, 7 Jul 2006 22:22:16 -0400
> > Matt Reuther <mreuther@umich.edu> wrote:
> >
> > > Here is the error:
> > > CHK include/linux/compile.h
> > > UPD include/linux/compile.h
> > > CC init/version.o
> > > LD init/built-in.o
> > > LD .tmp_vmlinux1
> > > arch/i386/kernel/built-in.o(.text+0xe282): In function
> > > `cpu_request_microcode':
> > > arch/i386/kernel/microcode.c:544: undefined reference to `request_firmware'
> > > arch/i386/kernel/built-in.o(.text+0xe304):arch/i386/kernel/microcode.c:573:
> > > undefined reference to `release_firmware'
> >
> > CONFIG_FW_LOADER=m
> > CONFIG_MICROCODE=y
> >
> > So
> >
> > config MICROCODE
> > tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
> > depends on FW_LOADER
> >
> > is not sufficient. There's a fix for this, but I cannot remember what it
> > is. Help.
>
> That 1-line depends patch fixes the problem for me (on x86-64,
> but they are the same in this area).
>
What patch is that?
next prev parent reply other threads:[~2006-07-09 3:44 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 [this message]
2006-07-09 4:37 ` Randy.Dunlap
2006-07-09 4:58 ` Andrew Morton
2006-07-09 7:20 ` Matt Reuther
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=20060708204448.6914aaf9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mreuther@umich.edu \
--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®