From owner-freebsd-wireless@freebsd.org Wed Mar 21 23:23:20 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2335FF4D66E for ; Wed, 21 Mar 2018 23:23:20 +0000 (UTC) (envelope-from fire@firecrow.com) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 B68C56E941 for ; Wed, 21 Mar 2018 23:23:19 +0000 (UTC) (envelope-from fire@firecrow.com) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 571BD21C96 for ; Wed, 21 Mar 2018 19:23:19 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Wed, 21 Mar 2018 19:23:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=PxWOYy WLZFdi/cXs5aMVrGEDhARtwiePkqbtW9PA60Q=; b=Qje94VYQila6HlCqRzyEqS W3Sa1QnD5+i5HrByoEcDmfFC0VRXJWdNPvgphezOLkZL97LKvB9V4GaaJOmmhrGG RJ29AhODC6vq1jtl1oH6qSG7HVY8XvG8gB98EZiT3G4+9MPFqzmSS8SwgDUKGguI QxNrT7WBUrmna9yVQwWjeI50oKy+wvA7z+PnnczcP43FtqMzLCnOvo9Ptxc0JQYN I5RbHKItnrRh8MZsg5zDG5q7zjKPl2clQ7dY61U77I6Wu5fL/QsFSzbv2J+Mdpzb QNZV/y6RTxAp3ShIuyYn5/R2iAgXB/YIoTVM8epa2m6Iv9xbn0iP1jHxItbUEiyg == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3D79A940A3; Wed, 21 Mar 2018 19:23:19 -0400 (EDT) Message-Id: <1521674599.2983319.1311638200.6D53CF18@webmail.messagingengine.com> From: Firecrow To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <1521674345.2981686.1311635920.0EABC8C2@webmail.messagingengine.com> In-Reply-To: <1521674345.2981686.1311635920.0EABC8C2@webmail.messagingengine.com> Date: Wed, 21 Mar 2018 16:23:19 -0700 Subject: Re: trying patch bwn for BCM4352 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 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, 21 Mar 2018 23:23:20 -0000 Hi all, sent this message while still composing it, I'm tying to get BCM4352 to work on my freebsd current machine. here is some information about my machine and what I've been trying uname -a FreeBSD ant.firecrow.com 12.0-CURRENT FreeBSD 12.0-CURRENT #3: Wed Mar 21 23:01:07 EDT 2018 I'm working under the assumption that the broadcom chipset is compatible with an existing driver it just needs the pci information linked in, so I've tried to add the interfaces to if_bwn_pci.c > > diff src.orig/sys/dev/bwn/if_bwn_pci.c src/sys/dev/bwn/if_bwn_pci.c > 54c54 > < static int attach_untested = 0; > --- > > static int attach_untested = 1; > 86a87,89 > > BWN_BCM_DEV(BCM4352_D11AC , "BCM4352 802.11n Dual-Band:/", 0), > > BWN_BCM_DEV(BCM4352_D11AC2G, "BCM4352 802.11n 2G:/", 0), > > BWN_BCM_DEV(BCM4352_D11AC5G, "BCM4352 802.11n 5G:/", 0), > 91d93 > < > 306a309 > > dmesg shows that it recognizes the device, but the usual information from a network device is not listed, as if the device is registered but not treated as a network device. > dmesg | grep bwn > bwn_pci0: mem > 0xfc600000-0xfc607fff,0xfc400000-0xfc5fffff irq 35 at device 0.0 on pci6 > bhndb0: on bwn_pci0 > bhndb0: Using MSI interrupts on bwn_pci0 all help welcome ~fire