2007/10/24, Eric W Anderson <Eric.Anderson@xxxxxxxxxxxx>: > I realize that primary role of the driver is for actual use, rather than for > research, but... It's very useful in experiments to have /proc entries for all > the settings that you don't normally think of as tunable. (e.g. turning off > antenna diversity, or ACKs, or changing the CCA thresholds). I'd really hate for > knobs to go away because someone things they're not "really" needed, or because > they're not worth merging into the new configuration framework. > > -Eric > We don't say that these values (eg. diversity) should not be tweaked, we say that /proc isn't the right solution. Also have in mind that for some of these we don't know if they work ok with the reverse engineered HAL, eg. i'm not sure that disabling rx diversity works because we haven't tested current hw_setdefantenna implementation (disabling tx diversity should work by passing a proper antenna value on setup_tx_desc but diversity is something that we might handle on mac80211, /proc's purpose is not doing configuration stuff). Actually only tweakable values at the moment are the calibration interval (very few people will play with that) and debug (which is a mask for enabling various debug messages) and i think they are both useless for someone not working on the driver. You can always use madwifi with the binary HAL for such stuff and research. Tweaking is not a priority right now for ath5k, we have to make things working before we start tweaking (eg. we can't tweak diversity when we still work on phy initialization)... -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
