Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Mar 2006 21:10:44 +0100
From:      Florent Thoumie <flz@xbsd.org>
To:        Sergey Matveychuk <sem@FreeBSD.org>
Cc:        ports@FreeBSD.org, damien@FreeBSD.org
Subject:   Re: RFC: New firmware ports for ipw(4) and iwi(4)
Message-ID:  <67109E0C-7F70-480E-9B24-1E69010C5F42@xbsd.org>
In-Reply-To: <4419C0F9.8010004@FreeBSD.org>
References:  <1142511875.823.83.camel@mayday.esat.net>	 <4419ACC7.2010009@FreeBSD.org> <1142533990.823.122.camel@mayday.esat.net> <4419C0F9.8010004@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 16, 2006, at 8:48 PM, Sergey Matveychuk wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Florent Thoumie wrote:
>> If your iwi(4) driver depends on firmware(9) then you don't need
>> iwi-firmware anymore. Check the output of kldstat -v.
>
> There is no iwi_bss there.
>
>>
>>> Nothing changed. A firmware does not load with the same diagnostic.
>>>
>>> I have CURRENT a day or two old.
>>
>> An error message would help :-)
>>
>
> I'm not sure:
>
> firmware_get: failed to load firmware image iwi-bss
> iwi0: could not load firmware image 'iwi-bss'
>
> The lines repeated for four times.
>
> But I can 'kldload iwi_bss' after booting. But it's  does not helps.

I have the same bug, I think ipw(4) and iwi(4) should try to load  
{ipw,iwi}_{bss,ibss,monitor}_fw, not just {ipw,iwi}_ 
{bss,ibss,monitor}, or subr_firmware should add "_fw" itself  
automatically.


-- 
Florent Thoumie
flz@FreeBSD.org
FreeBSD Committer





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67109E0C-7F70-480E-9B24-1E69010C5F42>