Re: [ath5k-devel] Master mode in ath5k

2010-07-22 Thread Pavel Roskin
On Thu, 2010-07-22 at 18:30 -0400, Aditya Bhave wrote: > Does ath5k support Master mode and half and quarter channel widths? Master mode is supported. Half and quarter channel widths are not supported. As far as I know, no support for non-standard channel widths planned. -- Regards, Pavel Ros

Re: [ath5k-devel] [RFC] refactor ath9k_platform to sound sane for use in both ath9k and ath5k

2010-07-22 Thread Daniel Golle
Hi! In order to support the Senao EAP7660D board, I now added ath5k_platform.h and patched ath5k (and madwifi). In this way, the infrastructure for ath9k and ath5k remains separate, as discussed in https://lists.openwrt.org/pipermail/openwrt-devel/2010-July/007506.html Is there any chance to hav

[ath5k-devel] Master mode in ath5k

2010-07-22 Thread Aditya Bhave
Hi, Does ath5k support Master mode and half and quarter channel widths? Thanks regards, Aditya Bhave ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Re: [ath5k-devel] [patch -next] ath5k: snprintf() returns largish values

2010-07-22 Thread Dan Carpenter
On Thu, Jul 22, 2010 at 10:56:13AM +0200, Jiri Slaby wrote: > On 07/22/2010 10:52 AM, Dan Carpenter wrote: > > snprintf() returns the number of characters that would have been written > > (not counting the NUL character). So we can't use it as the limiter to > > simple_read_from_buffer() without

Re: [ath5k-devel] [PATCH/RFC 3/3] ath5k: trace resets

2010-07-22 Thread Bruno Randolf
On Wed July 21 2010 16:53:21 Johannes Berg wrote: > On Wed, 2010-07-21 at 14:17 +0900, Bruno Randolf wrote: > > but that's for all tracepoints all over the kernel... > > Well you definitely don't want to enable like function graph tracing, > that's expected to be more expensive unless you also hav

Re: [ath5k-devel] [patch -next] ath5k: snprintf() returns largish values

2010-07-22 Thread Jiri Slaby
On 07/22/2010 10:52 AM, Dan Carpenter wrote: > snprintf() returns the number of characters that would have been written > (not counting the NUL character). So we can't use it as the limiter to > simple_read_from_buffer() without capping it first at sizeof(buf). Doesn't scnprintf make more sense

[ath5k-devel] [patch -next] ath5k: snprintf() returns largish values

2010-07-22 Thread Dan Carpenter
snprintf() returns the number of characters that would have been written (not counting the NUL character). So we can't use it as the limiter to simple_read_from_buffer() without capping it first at sizeof(buf). Signed-off-by: Dan Carpenter diff --git a/drivers/net/wireless/ath/ath5k/debug.c b