2009/4/16 Alina Friedrichsen <x-al...@gmx.net>: > Hello Nick! > >> * Add code to support the various antenna scenarios supported by hw >> >> * For now hardcode the default scenario (single or dual omnis with >> tx/rx diversity working and tx antenna handled by session -hw keeps >> track on which antenna it got ack from each ap/station and maps each >> ap/station to one of the antennas-). > > We should add or update an existing nl80211 call, to allow set the used > antenna (multiple antennas in Draft-N?) manually, like madwifi does. This is > e.g. needed for long distance links. > > Regards > Alina >
Well it's more complicated than that, we can only set tx antenna when using a sectored ap/sta scenario (else it's possible to miss rts and self generated frames), and we can only set default antenna on scenarios that don't update the default antenna dynamicaly. Here is a more detailed explanation of antenna scenarios... http://kerneltrap.org/mailarchive/linux-ath5k-devel/2008/11/26/4241174 I agree that one should be able to set rx/tx antenna from nl80211 (after all mac80211 has tx antenna information) but we also need a way to handle antenna scenarios. Setting antennas without setting the proper antenna scenarios will break things (as it did for mesh on the above mail). -- 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
