> > 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
