On Wed, Sep 30, 2009 at 08:14:57AM -0700, Matt Tierney wrote: > This might be a naive question, but I was wondering if it's > possible to set the MCS index either from a high level interface > or through a hack in the ath9k code. I'd like to fix the MCS Index > to 15 but I don't know where that is set or if I can 'force' it > through modifying the ath9k code in wireless-testing. (It doesn't > appear as if iw provides that sort of functionality and it wasn't > clear that I could specify a HT rate in hostapd.conf.) mac80211 rate control code is MCS rate unaware, but we do at least let drivers pass the MCS rate for tx status reporting. ath9k unfortunately reports back the wrong MCS rate though because of the way ath9k rate control works... it seems correcting this requires a rewrite of our ath9k rate control code and no one has prioritized on that as its a non-functional fix. The first step then is to make mac80211 rate controle code MCS aware and adding MCS rate control support to minstrel, for example. For ath9k it'd be nice to fix the rate control code to be able to report the right MCS index, I really am not sure how involved that is as I've tried to stay away from the rate control code. A good step would be to get ath9k rate control to be switchable to minstrel, for example. This can be done as a module parameter to start but eventually I think it'd be nice to be able to switch through iw on any given device. That would require quite a lot of work though. Once mac80211 is MCS rate control aware the next step would be to add a commands to set an MCS rate. The cheesy and quick way to this for ath9k would be through ath9k/debufs.c Luis -- 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
