Closed olerem closed 11 years ago
I move discussion here. That was wrong request.
Hm,
so it turns out the stbc rx handling is right - the API has two bits, and you can get away with setting just 1 bit for 1xSTBC
why are you ripping out the STBC capability matching?
i remove all unused checks. Do you mean htcap flags?
ping
Yes, you're right. If we use capinfo as "config" rather than as "what the peer announced", we can kill the STBC capability code and checks. Otherwise, we need to keep them and check both capinfo and TX STBC capability before we can transmit them.
Make sense?
yes, i'll prepare patches.
Remove some useless STBC parts and make code more readable