Date: Fri, 25 Apr 2008 15:31:05 +1200 From: Andrew Thompson <thompsa@FreeBSD.org> To: Ben Kaduk <minimarmot@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: CFT: 802.11 vap code Message-ID: <20080425033105.GD49280@citylink.fud.org.nz> In-Reply-To: <47d0403c0804242001n6a6c7c3fgcca03068b85084d9@mail.gmail.com> References: <480294E2.1000907@errno.com> <47d0403c0804242001n6a6c7c3fgcca03068b85084d9@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, Apr 25, 2008 at 03:01:29AM +0000, Ben Kaduk wrote: > Hi Sam, > > On 4/13/08, Sam Leffler <sam@errno.com> wrote: > > A patch to integrate my multi-bss (aka vap) support for wireless can be > > found here: > > > > http://www.freebsd.org/~sam/vap-2008051300.sh.gz > > > [sip] > > Note there are a few new drivers included: iwn (Intel 4965), bwi > > (Broadcom 43xx), and mwl (Marvell 88W8363). The iwn driver is > > unfinished; it should support 802.11n but progress has been slow > > due to poor vendor involvement. The bwi driver is experimental and > > folks are encouraged to help sephe get it into shape for commit (it > > currently is not ready CVS). mwl is provided as an example of a > > Sorry to jump in so late, but I just got a chance to compile this a couple > days ago. > > Is this vap code the same one that was committed? Something seems > to have confused my wireless card a great deal, possibly in the initialization > steps. I have a broadcom chip that will hopefully eventually be supported > by bwi, but I have been using ndis otherwise. > With a recompiled ndisulator driver, ifconfig up-ing the interface causes > the machine to panic; a vanilla ifconfig does not, but clearly the driver > is confused. This has been fixed and the entire code has been committed to CVS. I would recommend that you dont test Sams patch but rather update your box to the latest sources and try that. Andrewhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080425033105.GD49280>