Message-ID: <4979E67D.5040604@turknet.net.tr>
Date: Fri, 23 Jan 2009 17:47:09 +0200
From: Tarkan Erimer <tarkan.erimer@turknet.net.tr>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
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
References: <49771D65.3090205@turknet.net.tr> <20090121152818.GA3438@x200.localdomain> <497870A3.4070200@turknet.net.tr> <20090122203252.GA3258@xw6200.broadcom.net>
In-Reply-To: <20090122203252.GA3258@xw6200.broadcom.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1170
Lines: 27

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/