From: Tarkan Erimer <tarkan.erimer@turknet.net.tr>
To: Matt Carlson <mcarlson@broadcom.com>
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: Fri, 23 Jan 2009 17:47:09 +0200 [thread overview]
Message-ID: <4979E67D.5040604@turknet.net.tr> (raw)
In-Reply-To: <20090122203252.GA3258@xw6200.broadcom.net>
Matt Carlson wrote:
> 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.
>
>
Yep, you are right. It looks to me a bit like standard kernel compile
process' fault/bug.
Because all the previous kernel versions prior to 2.6.29-rc1/2 work
flawlessly.
next prev parent reply other threads:[~2009-01-23 15:47 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
2009-01-23 15:47 ` Tarkan Erimer [this message]
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=4979E67D.5040604@turknet.net.tr \
--to=tarkan.erimer@turknet.net.tr \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
/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