Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

[Jaswinder Singh Rajput]

On Thu, Jan 22, 2009 at 6:42 PM, Tarkan Erimer
<tarkan.erimer@turknet.net.tr> 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.
>
>

Is this ubuntu's specific problem or you also getting these
warnings/errors on another releases.

--
JSR

Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

[Tarkan Erimer]

Jaswinder Singh Rajput wrote:
> Is this ubuntu's specific problem or you also getting these
> warnings/errors on another releases.
>
>   
Yes,it's specific to Ubuntu's kernel build process (make-kpkg). I had no 
time to try with regular kernel build process. But; if it's necessary, I 
can try it out. BTW, my box is Kubuntu 8.10 with latest updates.

Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

[Tarkan Erimer]

Tarkan Erimer wrote:
> Jaswinder Singh Rajput wrote:
>> Is this ubuntu's specific problem or you also getting these
>> warnings/errors on another releases.
>>
>>   
> Yes,it's specific to Ubuntu's kernel build process (make-kpkg). I had 
> no time to try with regular kernel build process. But; if it's 
> necessary, I can try it out. BTW, my box is Kubuntu 8.10 with latest 
> updates.
>
Now, I tried with 2.6.29-rc2-git2 and the result is same. No difference. 
When I have time, I'll try via regular kernel compile process to see 
what will be happen.


PS: If you write a reply to "netdev@vger.kernel.org", it will not reach 
to me. Because, I'm not subscribed to this mailing-list. So, please CC 
it to me.

Tarkan ERIMER

Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

[Matt Carlson]

On Tue, Jan 27, 2009 at 07:48:44AM -0800, Tarkan Erimer wrote:
> Tarkan Erimer wrote:
> > Jaswinder Singh Rajput wrote:
> >> Is this ubuntu's specific problem or you also getting these
> >> warnings/errors on another releases.
> >>
> >>   
> > Yes,it's specific to Ubuntu's kernel build process (make-kpkg). I had 
> > no time to try with regular kernel build process. But; if it's 
> > necessary, I can try it out. BTW, my box is Kubuntu 8.10 with latest 
> > updates.
> >
> Now, I tried with 2.6.29-rc2-git2 and the result is same. No difference. 
> When I have time, I'll try via regular kernel compile process to see 
> what will be happen.

Like I outlined in my previous email, this is a scripting / tools problem.
Updating your kernel will not help.  Either the script or modinfo needs to
be modified to somehow recognize that while the driver does make
request_firmware() calls, the firmware resides in the kernel itself.

> PS: If you write a reply to "netdev@vger.kernel.org", it will not reach 
> to me. Because, I'm not subscribed to this mailing-list. So, please CC 
> it to me.
> 
> Tarkan ERIMER
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: [BUG] tg3 module problem on Linux-2.6.29-rc1-2

[Tarkan Erimer]

Matt Carlson wrote:
> On Tue, Jan 27, 2009 at 07:48:44AM -0800, Tarkan Erimer wrote:
>   
>> Tarkan Erimer wrote:
>>     
>>> Jaswinder Singh Rajput wrote:
>>>       
>>>> Is this ubuntu's specific problem or you also getting these
>>>> warnings/errors on another releases.
>>>>
>>>>   
>>>>         
>>> Yes,it's specific to Ubuntu's kernel build process (make-kpkg). I had 
>>> no time to try with regular kernel build process. But; if it's 
>>> necessary, I can try it out. BTW, my box is Kubuntu 8.10 with latest 
>>> updates.
>>>
>>>       
>> Now, I tried with 2.6.29-rc2-git2 and the result is same. No difference. 
>> When I have time, I'll try via regular kernel compile process to see 
>> what will be happen.
>>     
>
> Like I outlined in my previous email, this is a scripting / tools problem.
> Updating your kernel will not help.  Either the script or modinfo needs to
> be modified to somehow recognize that while the driver does make
> request_firmware() calls, the firmware resides in the kernel itself.
>
>   
I got it. Sorry for the noise.