Date: Sat, 25 Jan 2003 11:47:00 -0800 From: Sean Chittenden <sean@chittenden.org> To: Sam Leffler <sam@errno.com> Cc: "M. Warner Losh" <imp@bsdimp.com>, b@etek.chalmers.se, current@FreeBSD.org Subject: Re: HEADS UP: new wi driver Message-ID: <20030125194700.GA91522@perrin.int.nxad.com> In-Reply-To: <1cd401c2c499$ceec0590$52557f42@errno.com> References: <1e4301c2bd82$03de8cb0$5a557f42@errno.com> <Pine.BSF.4.44.0301171716010.49553-100000@scrooge.etek.chalmers.se> <20030117.102821.89423323.imp@bsdimp.com> <20030124215212.GB1224@perrin.int.nxad.com> <1cd401c2c499$ceec0590$52557f42@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> dstumbler uses WI_RID_SCAN_REQ to initiate a scan for AP's. This > required the application know whether it was talking to a > prims/wavelan/symbol card so was replaced by WI_RID_SCAN_APS which > provides a device-independent interface. I changed wicontrol to > deal with this; it would be good if dstumbler did likewise. > Otherwise I can look at adding a backwards compatibility entry for > WI_RID_SCAN_REQ. I've updated the sources with the new wlan request type and I'm not getting anyfurther than before. All of the bsd-airtools have all kinds of nifty hacks to support the various interfaces and quirks of each of the cards. I think I'm going to dable with the various bsd-airtools and update them to use the same interface that wicontrol does and see if I can't kill off as many card specific quirks as I can. -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030125194700.GA91522>