From owner-freebsd-current  Fri Jan 17  8:34: 7 2003
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 F043B37B401; Fri, 17 Jan 2003 08:34:05 -0800 (PST)
Received: from scrooge.etek.chalmers.se (scrooge.etek.chalmers.se [129.16.32.112])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A629C43F43; Fri, 17 Jan 2003 08:34:03 -0800 (PST)
	(envelope-from b@etek.chalmers.se)
Received: from scrooge.etek.chalmers.se (b@localhost [127.0.0.1])
	by scrooge.etek.chalmers.se (8.12.3/8.12.3) with ESMTP id h0HGXqca006256;
	Fri, 17 Jan 2003 17:33:52 +0100 (CET)
	(envelope-from b@etek.chalmers.se)
Received: from localhost (b@localhost)
	by scrooge.etek.chalmers.se (8.12.3/8.12.3/Submit) with ESMTP id h0HGXpOt006149;
	Fri, 17 Jan 2003 17:33:52 +0100 (CET)
X-Authentication-Warning: scrooge.etek.chalmers.se: b owned process doing -bs
Date: Fri, 17 Jan 2003 17:33:51 +0100 (CET)
From: Magnus B{ckstr|m <b@etek.chalmers.se>
To: Sam Leffler <sam@errno.com>
Cc: Sean Chittenden <seanc@FreeBSD.org>, 47A <current@FreeBSD.org>,
	Warner Losh <imp@village.org>
Subject: Re: HEADS UP: new wi driver
In-Reply-To: <1e4301c2bd82$03de8cb0$5a557f42@errno.com>
Message-ID: <Pine.BSF.4.44.0301171716010.49553-100000@scrooge.etek.chalmers.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

> > NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
> > to be resolved or documented before MFC.  (copied maintainer)
>
> Why, did they not work/build after the commit?  I didn't try all the ports
> that depend on the driver but the API (ioctls) should be unchanged except
> for the AP scanning stuff which is why I had to make mods to wicontrol.

Ok, this is what's up with bsd-airtools:
dstumbler breaks; on startup it reports
    "unable to ioctl device socket: Input/output error".

I gross-hacked dstumbler to record what it is really trying to
do (I won't decipher the ioctl cmd just now):

    ioctl(<an AF_INET SOCK_DGRAM socket>,
          0x80206939,
          <a struct ifreq>);

    the ifreq is initialized to zeros except ifr_data, which
    points at a struct wi_req containing the following:

wi_req = {
    0x0001,	/* wi_len */
    0xfce1,	/* wi_type */
    {
	0x0000,
        ... /* full of zeros */
	0x0000,
    }	/* wi_val[WI_MAX_DATALEN] */
}

The card is a Lucent Orinoco as follows:
wi0: <WaveLAN/IEEE> at port 0x100-0x13f irq 11 function 0 config 1 on pccard1
wi0: 802.11 address: 00:02:2d:1d:25:98
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.10.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

Hope this helps,
Magnus


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message