From owner-freebsd-wireless@FreeBSD.ORG Mon Feb 2 07:32:47 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91D1859F for ; Mon, 2 Feb 2015 07:32:47 +0000 (UTC) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A18EA70 for ; Mon, 2 Feb 2015 07:32:47 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id x12so36983767wgg.4 for ; Sun, 01 Feb 2015 23:32:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-type; bh=2Qi/lRB30NG0m33XNxA7/daOZK+SzmJfzS9Cfzu1rJI=; b=oPbRru9Al7T9Ld/pQf8+iBrMBP9xoWAm0pVBRFX+DC6CtEkOfHsIr2GWrAHosQKvMu +cSEEAXXh+3iZo75qI+8Sk40v31SKx7nVvHbvY4KiN6+JBYpsXeIfeSm+Jy0dr618+X9 N1+0n1B0vUkJNj9OP1FXhrZjxY5PVKs3UPBBfAvaH1IJcgjb7QRnANDf6Dgp6Fbqk0ct Ex4NFh+LDzNqfmiyju7vw7YAAj91OLftj8hUMIvILIq9qZgolSVheWITsBG9j4xYrdoE X0EOxxayAqT+7QLmR+MXTr7/yGvbPpPqZqiHNsJkPjFtb2bs48omLj+vLuYCMMhYljur 2NIA== X-Received: by 10.194.239.72 with SMTP id vq8mr30308093wjc.110.1422862365287; Sun, 01 Feb 2015 23:32:45 -0800 (PST) Received: from planb.netng.org (ip-78-45-45-166.net.upcbroadband.cz. [78.45.45.166]) by mx.google.com with ESMTPSA id hv5sm26558048wjb.16.2015.02.01.23.32.43 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 01 Feb 2015 23:32:44 -0800 (PST) Date: Mon, 2 Feb 2015 08:32:28 +0100 From: Vladimir Botka To: FreeBSD Wireless Subject: Re: How to make working new Broadcom chips like BCM4331? Message-ID: <20150202083228.4fc9defb@planb.netng.org> In-Reply-To: <0414D0A4-0E76-41AE-B043-453FDCBE1BCB@me.com> References: <0414D0A4-0E76-41AE-B043-453FDCBE1BCB@me.com> Organization: na X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/Wton0fIZlaLCY3dOSCRb+W4"; protocol="application/pgp-signature" Cc: Alexander Perechnev 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: Mon, 02 Feb 2015 07:32:47 -0000 --Sig_/Wton0fIZlaLCY3dOSCRb+W4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, On Mon, 02 Feb 2015 08:12:17 +0300 Alexander Perechnev wrote: > Hello everyone, >=20 > I=E2=80=99ve installed FreeBSD 10.1 on my MacBook Pro 13 mid 2012. Everyt= hing > 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, plea= se > let me know before I go through this steps. >=20 > Thank you for excellent operating system, now it=E2=80=99s my favorite on= e! >=20 > Best regards, > Alexander Perechnev. > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org" Hi, out of curiosity I reviewed the BCM status. 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 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 ,there is no support in the Linux kernel atm https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 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 Cheers, -vlado --Sig_/Wton0fIZlaLCY3dOSCRb+W4 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUzygMAAoJEJDRmRKO1E8B1TQIAIdF8lw4nPogyqV02XW7/12c ozi26INEk+rhzxbRwMqbTXG+fapAVYMEEaDb/fmto6AJ2p85uKCjzy/FQVwOdXsz vErfXjJyfdrDp3KzyTXX6Z+UnSaOiGZJbWpBDUHcDaLdeR/BBQcFyU2jbmWkjtuZ TYtfBOFBXkBErzjLaUtVw4pkpyoGhmeBC0EGmDIGpKWM5SYyNmW0oBwiWLhcRCOU QDWkFd258oR2cuq9rDxMHBX8xmf24C8dgFwNJVgme7Olma7SrebV8GHAgRd5V6Fp sFM4X+tLJGuV3USWpDl09oaPkr2Kk8VqBz3SbrsfxXhzI5mL4oo6Cod0aKvcr2w= =FSoV -----END PGP SIGNATURE----- --Sig_/Wton0fIZlaLCY3dOSCRb+W4--