From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Tarkan Erimer" <tarkan.erimer@turknet.net.tr>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2
Date: Thu, 22 Jan 2009 12:32:52 -0800 [thread overview]
Message-ID: <20090122203252.GA3258@xw6200.broadcom.net> (raw)
In-Reply-To: <497870A3.4070200@turknet.net.tr>
On Thu, Jan 22, 2009 at 05:12:03AM -0800, Tarkan Erimer wrote:
> Alexey Dobriyan wrote:
> > # CONFIG_FIRMWARE_IN_KERNEL is not set
> >
> >
> > Try setting this option to =y.
> >
>
> Thanks for the reply. I tried with "CONFIG_FIRMWARE_IN_KERNEL=y" as you
> suggested. But, still I get the same warning.
> It looks like ubuntu's make-kpkg utility or kernel compile process do
> not care about "CONFIG_FIRMWARE_IN_KERNEL=y" and still building modules
> without firmware built-in.
The error message is coming from the
/usr/share/initramfs-tools/hook-functions script. You are right that
the script does not look at the config file for
CONFIG_FIRMWARE_IN_KERNEL=y, but I'm not sure if it should or not.
The script uses the command 'modinfo -F firmware tg3' to determine
whether or not it should include firmware images in the initrd. The
modinfo command simply inspects the tg3.ko module binary reports if the
module makes any firmware requests. Obviously this isn't the complete
picture.
Somewhere in this process, the script or modinfo needs to find out if
the kernel has firmware images builtin. How this gets accomplished is
probably best left to the script maintainers.
next prev parent reply other threads:[~2009-01-22 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 13:04 [BUG] tg3 module problem on Linux-2.6.29-rc1-2 Tarkan Erimer
2009-01-21 15:28 ` Alexey Dobriyan
2009-01-22 13:12 ` Tarkan Erimer
2009-01-22 20:32 ` Matt Carlson [this message]
2009-01-23 15:47 ` Tarkan Erimer
2009-01-27 6:30 ` Jaswinder Singh Rajput
2009-01-27 7:45 ` Tarkan Erimer
2009-01-27 15:48 ` Tarkan Erimer
2009-01-27 18:35 ` Matt Carlson
2009-01-28 15:10 ` Tarkan Erimer
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=20090122203252.GA3258@xw6200.broadcom.net \
--to=mcarlson@broadcom.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan.erimer@turknet.net.tr \
/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