From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: linux-kbuild@vger.kernel.org, netdev@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29-rc: unable to compile e100 firmware into kernel
Date: Sun, 1 Feb 2009 22:18:16 +0300 [thread overview]
Message-ID: <200902012218.20481.arvidjaar@mail.ru> (raw)
In-Reply-To: <4807377b0902011105l29e846c3r140212ac654efb93@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On 1 of February 2009 22:05:43 Jesse Brandeburg wrote:
> On Sat, Jan 31, 2009 at 7:59 AM, Andrey Borzenkov <arvidjaar@mail.ru>
wrote:
> > {pts/2}% LC_ALL=C make -C ~/src/linux-git
> > O=$HOME/build/linux-2.6.29 make: Entering directory
> > `/home/bor/src/linux-git'
> > Using /home/bor/src/linux-git as source for kernel
> > ln -fsn /home/bor/src/linux-git source
>
> I think (seem to recall something on the list) there have been
> multiple people reporting the make O= option doesn't work with
> CONFIG_FIRMWARE_IN_KERNEL, but what does the
> CONFIG_PREVENT_FIRMWARE_BUILD=y option do? If it does what it
> appears to by its title, looks like you might need to set that to =n
Does not work. Besides, even with CONFIG_PREVENT_FIRMWARE_BUILD=y
firmware is built and installed under /lib/firmware when
CONFIG_FIRMWARE_IN_KERNEL is not set. It is just that it does not help
with netconsole :(
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-01 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 15:59 2.6.29-rc: unable to compile e100 firmware into kernel Andrey Borzenkov
2009-02-01 19:05 ` Jesse Brandeburg
2009-02-01 19:18 ` Andrey Borzenkov [this message]
2009-02-04 13:33 ` David Woodhouse
2009-02-04 16:45 ` Andrey Borzenkov
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=200902012218.20481.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.