Date: Thu, 16 Mar 2006 21:38:32 +0100 From: Florent Thoumie <flz@xbsd.org> To: ports@FreeBSD.org Cc: damien@FreeBSD.org, Sergey Matveychuk <sem@FreeBSD.org> Subject: Re: RFC: New firmware ports for ipw(4) and iwi(4) Message-ID: <D9D20BC2-C53C-4FBD-B0A9-CFE0F5F35ED3@xbsd.org> In-Reply-To: <67109E0C-7F70-480E-9B24-1E69010C5F42@xbsd.org> References: <1142511875.823.83.camel@mayday.esat.net> <4419ACC7.2010009@FreeBSD.org> <1142533990.823.122.camel@mayday.esat.net> <4419C0F9.8010004@FreeBSD.org> <67109E0C-7F70-480E-9B24-1E69010C5F42@xbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 16, 2006, at 9:10 PM, Florent Thoumie wrote:
> 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.
Well, not true, the module name and the firmware name were a bit
confusing for me. Not sure why it doesn't work. I'm investigating.
--
Florent Thoumie
flz@FreeBSD.org
FreeBSD Committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D9D20BC2-C53C-4FBD-B0A9-CFE0F5F35ED3>