From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 24 11:19:18 2010 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16F8A1065672 for ; Sun, 24 Jan 2010 11:19:18 +0000 (UTC) (envelope-from jensthiede@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9CC8FC18 for ; Sun, 24 Jan 2010 11:19:17 +0000 (UTC) Received: by ewy3 with SMTP id 3so1357178ewy.13 for ; Sun, 24 Jan 2010 03:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=9SUovm0fKO4/kcr4AH6mp1XG5JB+Ni7cjBjLRU3X+aU=; b=Aq3e4nOYLzzaalVkb4sVkzRkYJ/TRqtUjmGZqHCRubuZYJ4udjJLvDNHsY36+yV5vi cjaFmXohNCQpe1oRPDMuKw1xd41ixuM2lKmTHoTQkroMpvbziU3GzRQB9+YWwPoRR6OE fmEXVW5e2jO7VeSym7594wNVVEKEOfWDVJeW4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=jj4JkVvol1YntfpH2tKwLTf5N/sFOjreV/0PGadj0fbwIECyhmzs9zBvBE0sHV6wpm XBwOJrw8Z7J0kYl7YZ5i3qkczUytZuND8RE6d6oaUvcDw9p1oc3wGbAcV144JZyuiiCi ljLlUiZek1bCdL3VDbCzJt3QxvIYQGri3xLBk= Received: by 10.213.109.141 with SMTP id j13mr2225415ebp.85.1264331956264; Sun, 24 Jan 2010 03:19:16 -0800 (PST) Received: from ?192.168.0.6? (wbs-41-208-196-17.wbs.co.za [41.208.196.17]) by mx.google.com with ESMTPS id 5sm4236051eyf.0.2010.01.24.03.19.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 24 Jan 2010 03:19:15 -0800 (PST) Message-Id: <513691FA-C112-414D-A844-66F24DD43142@gmail.com> From: Jens Thiede To: freebsd-mobile@freebsd.org In-Reply-To: <4B5BA593.2080408@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 24 Jan 2010 13:19:10 +0200 References: <3FD5CEEC-C167-4379-91CB-81DB8C9CEC0F@gmail.com> <20100123182818.5faa7868.torfinn.ingolfsen@broadpark.no> <4B5BA593.2080408@freebsd.org> X-Mailer: Apple Mail (2.936) Subject: Re: Intel PRO/Wireless 2100 DIY Bug Fix X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2010 11:19:18 -0000 On 24 Jan 2010, at 3:42 AM, Sam Leffler wrote: > Jens Thiede wrote: >> Thank you, I'll take that into account. >> >> Something must have changed from 7.0. Is there a documented API for >> NICs? It would help to know what's new and what's not > > There is documentation for the net80211 subsystem in section 9 of the > man pages. > > , since I'm new to >> FreeBSD. Or is there just code and no documentation? >> >> Jens >> >> On 23 Jan 2010, at 7:28 PM, Torfinn Ingolfsen wrote: >> >>> Hello, >>> >>> On Sat, 23 Jan 2010 18:54:07 +0200 >>> 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 >>> >>> Please note: I have seen the message "need multicast update >>> callback" >>> on other nics (not ipw) under 8.0-stable, and those nics work, so I >>> don't think that this message tells you why the ipw 2100 doesn't >>> work. > > This diagnostic indicates the driver lacks support to push multicast > filtering to the h/w. This can be fixed either by fixing the driver > (if > the h/w is capable) or by adding s/w multicast filtering support in > the > kernel to handle it instead. When the latter is done then the > net80211 > code can be changed to enable that functionality when the driver lacks > support for pushing the multicast list into the h/w. > > This issue has been discussed numerous times but noone has stepped > up to > fix the ALLMULTI support. > > Sam Well, I'll see what I can do about the 2100 problem, though, I don't know if I'll have any success. Thanks greatly for pointing me to the documentation. Jens.