From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 1 21:43:07 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 5C6AE881 for ; Wed, 1 Apr 2015 21:43:07 +0000 (UTC) Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (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 28191E86 for ; Wed, 1 Apr 2015 21:43:07 +0000 (UTC) Received: by pdrw1 with SMTP id w1so59394733pdr.0 for ; Wed, 01 Apr 2015 14:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=+JGCP9BDuzR4tTjdqk+c/yMwmMNUcEOXs1Fc0UvAwNo=; b=EYT9lX4PP30o5FqWKDyUR8q+7Gpu57gBZtawPToKn2tezO1W8X9Sht7t9kVMK4F16S baNsNyESHSb1twWToneEqOaWLY7lkFJkRq4J6jKQasY4s4u9G3QIamRdrvXapiphCPSY bU7S955fs6zkZhlWSGQYUNOASMQe8SNLuPxB+vN2l7pC58g9DDmoXaVXCXlTagqF+D2z oRyo5Os1CU5jl1EujbX+DqEqzxNw/2rebX2krt1vv9dXm+S8Spcqfm82VR27KNWa7Tdt 3cJ9aMl2hHMz4aVtvXaQBexzKNTyMtWIM/jzXH7C9HPZmTuEjz/3bCEAivSloQNJTZb1 DQyw== X-Received: by 10.68.180.195 with SMTP id dq3mr32474919pbc.39.1427924586518; Wed, 01 Apr 2015 14:43:06 -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 pf10sm3047345pbb.93.2015.04.01.14.43.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 14:43:05 -0700 (PDT) From: Felix Friedlander Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: How to make working new Broadcom chips like BCM4331? Message-Id: <2D66DCCB-AAC5-4431-BC3E-57877979B8D9@gmail.com> Date: Thu, 2 Apr 2015 08:42:55 +1100 To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2093\)) X-Mailer: Apple Mail (2.2093) 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: Wed, 01 Apr 2015 21:43:07 -0000 > 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? 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 -- Felix Friedlander