From owner-freebsd-drivers@FreeBSD.ORG Sun Jan 31 18:53:52 2010 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFABD106566C; Sun, 31 Jan 2010 18:53:52 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 83CDE8FC16; Sun, 31 Jan 2010 18:53:52 +0000 (UTC) Received: from ice.local ([10.0.0.115]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id o0VIrp6S080551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Jan 2010 10:53:51 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4B65D1BF.2000809@errno.com> Date: Sun, 31 Jan 2010 10:53:51 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: John Baldwin References: <60E5C138-F61F-4F00-AC19-AD3CDC151451@gmail.com> <201001220930.11859.jhb@freebsd.org> <4B5BA5FA.5050108@freebsd.org> <201001250836.07337.jhb@freebsd.org> In-Reply-To: <201001250836.07337.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-drivers@freebsd.org Subject: Re: Intel PRO/Wireless 2100 DIY Bug Fix X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2010 18:53:52 -0000 John Baldwin wrote: > 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. > ipw was documented as broken in the 8.0 release notes. Sam