On 2010-11-10 4:52 PM, Johannes Berg wrote: > On Wed, 2010-11-10 at 12:50 +0900, Bruno Randolf wrote: > >> 802.11n devices should enable or disable chains, based on which antennas are >> present (If all antennas belonging to a particular chain are disabled, the >> entire chain should be disabled). HT capabilities (like STBC, TX Beamforming, >> Antenna selection) should be calculated based on the available chains after >> applying the antenna masks. Should a 802.11n device have diversity antennas >> attached to one of their chains, diversity can be enabled or disabled based on >> the antenna information. > > I'm not entirely convinced that this is a good idea. Nor that, even if > 11n devices were to implement it, they should all implementing their own > code to update the HT capabilities. However, I suppose that nothing > forces them to implement it, and when somebody does I can still complain > when they put everything into the driver. Drivers already need to calculate their HT capabilities based on the number of chains. If chains get masked out based on the antenna mask settings, the driver code would most of the time only need minor refactoring for updating the settings which wouldn't necessarily result in any new code duplication at all. - Felix -- 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