From owner-freebsd-embedded@freebsd.org Fri Oct 21 13:53:49 2016 Return-Path: Delivered-To: freebsd-embedded@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7487CC1BF71 for ; Fri, 21 Oct 2016 13:53:49 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39F4ADD8 for ; Fri, 21 Oct 2016 13:53:48 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-embedded@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bxaGY-002ujj-Rf>; Fri, 21 Oct 2016 15:53:46 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-embedded@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bxaGY-001xNU-JY>; Fri, 21 Oct 2016 15:53:46 +0200 Date: Fri, 21 Oct 2016 15:53:41 +0200 From: "O. Hartmann" To: freebsd-embedded@freebsd.org Subject: BCM43134 support in 12-CURRENT? Message-ID: <20161021155341.5efc4d1b@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 13:53:49 -0000 I have no experience with recent FreeBSD on Raspberry Pi 3B or Odroid-c2 SoC and I'm not aware of the recent development. I/we plan to use a small nanoBSD project for a joint-purpose device with either a Raspberry Pi 3B or/and Odroid-C2 as a host for several environmental sensors. The system's network attachment will be hard wired, but it would be highly appreciable to have an additional access point on such a device. The only device/SoC I'm aware of having a built-in WiFi chip is the new Raspberry Pi3B, its WiFi chip is supposed to be a Broadcom BCM43134. The chip is well supported by Linux drivers, but I couldn't find any informations about supported devices via FreeBSD's bwi/bwn drivers - they list several older devices. Since I plan to use 12-CURRENT due to the fact of an ongoing development and project's development of my own, my question would focus on CURRENT and its driver support. Is there support for this specific BCM chipset? To use this chipset as AP, there must be a driver supporting this - as far as I know. I would appreciate if you could CC me, I do not subscribe this list. Thanks in advance and kind regards, O. Hartmann