From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 2 01:39:54 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 717636AF for ; Thu, 2 Apr 2015 01:39:54 +0000 (UTC) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36075B3C for ; Thu, 2 Apr 2015 01:39:54 +0000 (UTC) Received: by pdrw1 with SMTP id w1so64685548pdr.0 for ; Wed, 01 Apr 2015 18:39:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=jNRO3b+7lC+S99cTFRvOuXkB2K/eE2VZ3DdyNm5xM+U=; b=t4fOF3Y67ShtYeOsHumsDoAuEnTt8HbZEXbgS79MzNAfOmi/fz7hXD3RS0liBQmsar MzEROT7i2GbBm+lHIMXAJzIMEUjqyP/aCq5sXxthrXOIyH0R03P9zUmGQKiW0yZPUcpA takS4K02sdN08YD3/Fd7lDvxEk3GkGLFwJrdxI8i6qipQDfvDBAFBp2m3e91lJs337a6 RiX9ids975312ao6o7xNDMufVavlb4+WOBq32FKY6cc2Th6Cw3OTt+eO4WpKxNuomgDJ qS9VGl8UCxDIhBt1sXRq4vvuxNpewue+a2H/7VeOCYUT+qoSN2lAcgjAce0srxCYS2h4 moAQ== X-Received: by 10.68.253.226 with SMTP id ad2mr81940464pbd.98.1427938793626; Wed, 01 Apr 2015 18:39:53 -0700 (PDT) Received: from [192.168.0.5] (c211-30-51-180.frank3.vic.optusnet.com.au. [211.30.51.180]) by mx.google.com with ESMTPSA id z6sm3372926pdm.78.2015.04.01.18.39.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 18:39:52 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2093\)) Subject: Re: How to make working new Broadcom chips like BCM4331? From: Felix Friedlander In-Reply-To: Date: Thu, 2 Apr 2015 12:39:42 +1100 Message-Id: References: <2D66DCCB-AAC5-4431-BC3E-57877979B8D9@gmail.com> To: Johannes Dieterich X-Mailer: Apple Mail (2.2093) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 01:39:54 -0000 > On 2 Apr 2015, at 9:12 am, Johannes Dieterich = wrote: >=20 > On Wed, Apr 1, 2015 at 11:42 PM, Felix Friedlander = > wrote: >>> Hi, >>>=20 >>> On Mon, 02 Feb 2015 08:12:17 +0300 >>> Alexander Perechnev wrote: >>>=20 >>>> Hello everyone, >>>>=20 >>>> I=E2=80=99ve installed FreeBSD 10.1 on my MacBook Pro 13 mid 2012. = Everything >>>> works pretty good, except wireless. It works with [ndis], but it >>>> doesn=E2=80=99t work with existing [bwi-firmware-kmod] and >>>> [bwn-firmware-kmod] facilities. >>>>=20 >>>> I=E2=80=99ve looked into [bwn] port Makefile >>>> = (https://github.com/aperechnev/freebsd-ports/blob/master/net/bwn-firmware-= kmod/Makefile) >>>> and found that all it does is just to download necessary firmware >>>> (4.150.10.5 and 4.178.10.4), extracts it via [b43-fwcutter-015] and >>>> compiles it into kernel module. >>>>=20 >>>> So the first problem is that 4th gen firmware does not support my >>>> BCM4331. >>>>=20 >>>> Also i=E2=80=99ve found the [siba-bwn], which recognizes the = broadcom >>>> devices: >>>> = https://github.com/freebsd/freebsd/blob/master/sys/dev/siba/siba_bwn.c. >>>>=20 >>>> So summary it seems that it is not so hard to support my BCM4331. I >>>> have to: >>>>=20 >>>> - port [b43-fwcutter-018] to FreeBSD, because earlier versions >>>> doesn=E2=80=99t work with newest firmware >>>> - update existing [bwn-firmware-kmod] to point it to newest = firmware >>>> - add my BCM4331 device to [siba-bwn] >>>>=20 >>>> I expect that after this steps my BCM4331 should be working. But I = am >>>> new in FreeBSD and I=E2=80=99m just asking you for any help like = related >>>> information, existing problems, links, etc. >>>>=20 >>>> I am not sure if I am right in my theory, but for me it seems that = it >>>> should work. So if you know another problems, which I don=E2=80=99t, = please >>>> let me know before I go through this steps. >>>>=20 >>>> Thank you for excellent operating system, now it=E2=80=99s my = favorite one! >>>>=20 >>>> Best regards, >>>> Alexander Perechnev. >>>> _______________________________________________ >>>> freebsd-wireless at freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to >>>> "freebsd-wireless-unsubscribe at freebsd.org" >>>=20 >>> Hi, >>>=20 >>> out of curiosity I reviewed the BCM status. >>>=20 >>> IMO you don't have to port the b43-fwcutter to BSD. It would be = nice, >>> but you can use any Linux to get the firmware (from /lib/firmware/). = For >>> example. >>> https://help.ubuntu.com/community/MacBookPro8-2/Oneiric#Wireless >>>=20 >>> As of the support, JFYI >>> BCM4331 Linux driver is provided by Broadcom >>> http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt >>>=20 >>> ,there is no support in the Linux kernel atm >>> https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 >>>=20 >>> and I'm not sure, where do the bwi/bwn drivers come from (to see how >>> probable is the support of BCM4331). >>> bwi -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver >>> bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver >>>=20 >>>=20 >>> Cheers, >>>=20 >>> -vlado >> Just out of curiosity, is anyone working on this ATM? I=E2=80=99ve = had the same problem, and it is (no offence to anyone intended) a bit = ridiculous that the latest Broadcom chips we support are around 5 years = old now. I don=E2=80=99t actually know enough to say this for sure, but = judging by the first message it looks like this is a (relatively) simple = fix - simply add newer firmware and sell siba to detect the new cards. = Is this the case, or am I misreading the whole situation? > Well, looking at the commit history of both the siba source and the > port containing the firmware binaries, I'd say the driver is in > maintenance mode since March 2010. Which nicely lines up with the five > year old chips, unfortunately. No idea if it is indeed as simple as > adding a few PCI-IDs and the binaries but if you have such a device, > maybe you could try it? I=E2=80=99ll try, however my coding skills are truly woeful :-). I have = access to devices with BCM4331 and BCM43224 (I=E2=80=99m a convert from = the Mac world), as well as older ones to make sure I don=E2=80=99t break = anything. >=20 >> Also, the Broadcom-provided linux STA driver you referenced above is = not very widely used - b43 (the kernel driver) is much more common, and = requires extracting the firmware just like the FreeBSD drivers. See = https://wireless.wiki.kernel.org/en/users/Drivers/b43 = > The page also claims that the operation of b43 is limited to 11g? Is > this correct? Nope, it=E2=80=99s not. b43 can do 11n for sure, not sure about 11ac or = others. b43 is a much more capable driver than the wl STA driver, and is = also open (as opposed to the STA which is sort-of, kind-of open = depending on who you ask). > Johannes -- Felix Friedlander