On 2012-07-12 8:27 AM, Sujith Manoharan wrote: > Felix Fietkau wrote: >> If the aggregate size exceeds the TXOP limit, it leads to lots of unnecessary >> hardware and software retries. >> >> The previous 4ms frame limit table was completely undocumented, the commit >> that updated it only vaguely referenced and equation from the standard, >> but I've been unable to replicate its results. >> >> Fix this by using a formula based on the code in ath_pkt_duration, which is >> more likely to be correct for this case. > > I think this needs to be verified. The 4ms restriction is for Japanese > regulatory compliance, IIRC. I did check the generated tables and also tested that it would not generate aggregates with a duration of more than 4ms. - 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
