From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 09:45:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7739F16A4CE for ; Mon, 7 Jun 2004 09:45:10 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC3CB43D5C for ; Mon, 7 Jun 2004 09:45:09 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id 16CB320F44 for ; Mon, 7 Jun 2004 11:45:04 +0200 (CEST) Received: by taz.hsc.fr (Postfix, from userid 1001) id 79A514659; Mon, 7 Jun 2004 11:45:08 +0200 (CEST) Date: Mon, 7 Jun 2004 11:45:08 +0200 From: Yann Berthier To: freebsd-current@freebsd.org Message-ID: <20040607094508.GA740@hsc.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <20040604122041.GB84468@shiva.int.ipv42.net> <20040604183553.8997916A4CF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040604183553.8997916A4CF@hub.freebsd.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 5.2-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: 802.11g/GPRS broadcom cardbus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 09:45:10 -0000 Hello, [Nicolas and I are coworkers] On Fri, 04 Jun 2004, Bill Paul wrote: > Hm. In theory, I think it's possible to make the whole thing work. > The only tricky part is that they've combined two functions on the > same device. The 802.11g wireless function should work fine using > the NDISulator and the supplied Windows driver (check the CD that > came with it: there's probably a bcmwl5.sys and bcmwl5.inf file on > it somewhere). But the probe routine in if_ndis_pci.c only selects > devices based on the PCI vendor and device ID. If the two functions > appear to have unique device IDs, then you should be ok. If not, the > probe routine might try to claim both the wireless function and > the serial function. > > If it turns out both functions have the same vendor/device ID, this > shouldn't be too hard to deal with: the probe routine can additionally > check the PCI device type code and reject anything that isn't 'network' > or 'wireless.' We have not tested the ndis part yet. > As for the serial interface, assuming it behaves like a normal > COM port, I expect you can get it to work by adding the PCI vendor/device > ID to the PCI attachment of the sio driver. Then it will get attached > as an sio device. Indeed it works, all it takes is to add { 0x432214e4, "Broadcom 802.11g/GPRS CardBus (Serial)", 0x10 }, In /usr/src/sys/dev/sio/sio_pci.c Do we need to submit a PR ?