Re: USB Wifi adapter (Atheros)

Paul B Mahol <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
On 10/25/10, Matthias Apitz <[email protected]> wrote:
> El dia Monday, October 25, 2010 a las 08:28:34AM +0000, Paul B Mahol
> escribio:
>
>> >> > I've tried as well the ndisgen(8) way based on the XP driver with no
>> >> > luck.
>> >>
>> >> And you reported bug?
>> >
>> > No. I have no problem with filing a bug report, but I was unsure if this
>> > makes sense because we are talking (at least in parts) about Windows
>> > software. Should I?
>>
>> If you tell me what you did and what did not work I could help you.
>
> Thanks for your kind offer.
>
> The laptop comes with Windows7 pre-installed and I've pulled out the
> files:
>
> BCMWL6.SYS
> netbc6.inf
>
> I run
>
> $ ndisgen netbc6.inf BCMWL6.SYS
>
> and it created the module BCMWL6_SYS.ko; and in addition I created
> bwi_v3_ucode.ko from the ports (don't know if this is also required for
> the ndis based driver).
It is not required for ndis miniport driver.
>
> Both get loaded on boot but the interface ndis0 does not show up and
> pciconf(8) shows the device without attached driver.
>
> The same is true when I use an older (2006) bcmwl5.* from XP. I don't
> have netbc6.inf BCMWL6.SYS for XP. Maybe this is the main fault...

As name suggest "6" means it use NDIS 6 API, NDISulator supports 5.1
and not 6 or higher.

Adding support for 6 API is in very early (planning) stage.

When you load bcwml5 driver what is displayed on console?
>
> I'm missing something?
>
> Thanks again
>
> 	matthias
>
> --
> Matthias Apitz
> t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
> e <[email protected]> - w http://www.unixarea.de/
>
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.