ephen. :) Some minor comments. Seems like dma-mapping.h, udp.h, tcp.h, irq.h don't need to be included for a clean compile. Ditch 'em? PFX instead of skge. There are a couple of
Hi, This list of stuff that should get fixed in Linux wireless grew out of my attempt to put a GUI on top of Linux wireless with NetworkManager (http://people.redhat.com/dcbw/NetworkManager). This is
Yes, I've seen your various contributions for the various drivers. I'm glad that someone is doing all these little fixes, because they are needed, and such a job is not gratifying and not well recogn
Quite true, and I don't think that's a bad approach, I just think that adding general WPA support to WEAPI a bit earlier might have saved some trouble. Since most driver writers have their drivers in
Only orinoco/hermes is in the kernel, and that doesn't really have much of an 802.11 stack, since most things are done in hardware. Madwifi has a fairly complete 802.11 stack (ported from netbsd), an
Hi. It does. The SIOCGIWSTATS is used in tools/athstats.c (line 195 in current CVS) for example to get the rssi (via qual.qual). o Ad-Hoc mode support is quite flaky or absent from most drivers Low p
One of the big item not mentionned by you is the in-kernel 802.11 stack (native frames and management). If done right, I guess it would mostly be transparent to you... You know, I was thinking of it
Except then there's no handler for it in the ath_handlers[] array: /Users/dan/Desktop/madwifi> grep -r "SIOCGIWSTATS" * ath/if_ath.c: (iw_handler) NULL /* kernel code */, /* SIOCGIWSTATS */ tools/ath
I'm not aware of any. The latest revision of the adm8211 chip supports more than one tx queue, but only one is used. -Michael Wu Attachment: pgpFLPVxfiGya.pgp Description: PGP signature
Hi. Some (most or all?) Atheros chipsets have several priority queues. As far as I can tell Madwifi is prepared for supporting them, as well as the underlying 802.11 stack that has been ported from B