Hi Adrian
That is OK, I have download the source code of Wifimgr, it use ifconfig. I
was using ifconfig wlan0 scan, it was to slow to display info, but in the
Wifimgr code they use
ifconfig -v wlan* list scan and ifconfig wlan* list scan. I also found
wifimgr calculate S:N to find the
I'd rather that the ioctl API be used, rather than the output of 'ifconfig'.
It's likely about time the ioctl API was turned into a library for userland
to use. That way it could be imported into python/etc via C bindings.
Thanks,
-adrian
On 15 October 2013 04:16, Eric Turgeon
On 10/15/2013 11:15, Adrian Chadd wrote:
Well, up until now the interactions have all been via the ioctl API or the
ifconfig command. Both are cumbersome.
There's a decent amount of library code in ifconfig for wifi and regulatory
related stuff. It could be broken out into a public library..
Hi all,
The initial AR934x support is now in the tree.
The basics:
* the basic hacks needed to bring up mips74k support is now in the tree;
* I've added MIPS bus space barriers to things;
* on-board wifi works;
* slow UART works (ie, rs232 console);
* on-chip switch support works (but no VLAN
The wireless API used to be the same as what's in Linux. So, in theory, we
could just use anything that used Linux wireless extensions. Save, of
course, the API drift.
So, you could just write a full wireless manager that used the ioctl API
for the basic manipulation of the VAP (eg link status,
I don't have any real answers for you. I'd look at the interframe spacing
and timing; see if it's due to big gaps in transmission/reception, see if
it's something silly like AMPDU density being way too big, or maybe just
lots of retries.
I'm sorry I can't be more helpful than this!
-adrian
Ok, so what, I should test out split_8, get that into the tree, then merge
in more stuff from you?
-adrian
On 14 October 2013 08:17, Cedric GROSS c...@cgross.info wrote:
De : Sean Bruno [mailto:sean_br...@yahoo.com]
À : Cedric GROSS
Cc : 'Adrian Chadd'; freebsd-wireless@freebsd.org
