2010/11/23 Luis R. Rodriguez <lrodrig...@atheros.com>: > On Tue, Nov 23, 2010 at 11:04:43AM -0800, Nick Kossifidis wrote: > > Are you willing to deal with *all* bug reports for this? > > Luis >
I don't enable 5/10/40MHz operation anywhere for now, it's just there for testing/debug. I tested it and it seems to work fine (also with a spectrum analyzer) but until we come up with the proper way to set this from user-space I'll wait. Also have in mind I just do what Atheros does on initvals, nothing new, I just diffed initvals/rfbuffer settings between turbo/non-turbo modes, found what's changing and how (i had 5/10MHz code from HAL for that -as i wrote on another mail 5/10/40MHz work mostly the same way-) and implemented it on code. Now it's much cleaner + it actually works so i don't see a problem with that. Before we had code for turbo that didn't work and duplicated arrays of initvals/rfbuffer settings for no reason. Have in mind that there are people out there that want 5/10MHz support badly to implement 802.11p on top of it (or for research) and people who want to get rid of MadWiFi on OpenWRT and use turbo mode with ath5k. We had to do this sometime, it's not a dirty hack, i think the implementation is clean and simple. As for bug reports we already have bug reports about cards that fail to wake up that we are unable to debug because we have no idea what's going on, you can't choose what you 'll do based on possible bug reports, bugs are part of the process... -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
