Johannes Berg wrote: > Not right now - and there's practically no space left in the rate u16 to > store it. > > Eyal also commented that perhaps not just antennas but also > STBC/LDPC/beamforming should be tracked. > > We can achieve this by increasing the size of the rate field to u32, but > then we also have far more combinations so probably need to increase the > size of the buffer from 36 entries to more since otherwise we just end > up sending the data out to userspace too frequently? Antennas for > example could change frequently for single stream rates. > > This capability right now is mostly intended for Android Lollipop's > statistics requirements, where the rate only matters. Ok. > If others want to use it for more, I'm certainly not averse to adding > it, but it'd also mean adding more userspace API (where it might be a > bit strange to add "antennas" to the "rate" since that doesn't impact > the actual rate?) Having a well-defined API to export statistics seems useful, but I guess that can be added later. Sujith -- 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
