Date: Mon, 25 Jan 2010 08:36:07 -0500 From: John Baldwin <jhb@freebsd.org> To: Sam Leffler <sam@freebsd.org> Cc: freebsd-drivers@freebsd.org Subject: Re: Intel PRO/Wireless 2100 DIY Bug Fix Message-ID: <201001250836.07337.jhb@freebsd.org> In-Reply-To: <4B5BA5FA.5050108@freebsd.org> References: <60E5C138-F61F-4F00-AC19-AD3CDC151451@gmail.com> <201001220930.11859.jhb@freebsd.org> <4B5BA5FA.5050108@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 23 January 2010 8:44:26 pm Sam Leffler wrote: > John Baldwin wrote: > > On Friday 22 January 2010 3:59:10 am Jens Thiede wrote: > >> Hi all, > >> > >> I'm pretty new to FreeBSD. However, I think I might be able to create > >> a patch for the Intel PRO/Wireless 2100 bug (http://bit.ly/7SWIQr). > >> > >> Seems likely that there's simply a callback missing. I take it the API > >> might have changed a little lately. Is there documentation for the > >> wireless networking API? Or is that simply something that I have to > >> figure out myself? Also, is there a relevant channel on Freenode where > >> I could ask short questions? I'd really like to have this driver > >> working. > >> > >> All help is much appreciated. > > > > I think the folks who work on the wireless drivers are usually more active on > > the mobile@ list, so you can try asking there. Also, was this broken by the > > recent MFC to 8 of iwn(4)? > > > > No, this is a longstanding issue w/ not having proper support for > IFF_ALLMULTI (sic?). The multicast message is a red herring. If you look at the PR at the URL above the actual bug is a failure to associate. It claims that this is a regression from 7 I believe where the card could associate ok under 7, but not under 8. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001250836.07337.jhb>