On 5 October 2012 09:51, Sven Eckelmann <sven@xxxxxxxxxxxxx> wrote: >> Well, is it a RX chainmask thing, or is it a chip thing? >> >> It's totally possible to have an RX chainmask of say 0x2 or 0x4.. > > What are you trying to tell us? That the check for "rx chainmask == 1? Definitely can't do MRC CCK" implying "rx chainmask != 1? Definitely can do MRC CCK." I think that's the wrong logic. It may be a general chipset problem across some/all AR9300 and later chips that doing MRC CCK with only one RX chain enabled is a problem, or it may be a single-chain NIC problem. I'm pretty sure we can configure any of the RX antennas; it doesn't have to be "one chain == chain 0." Anywy. I'll double check that. > Maybe you missed that part of the conversation, but this was exactly what I > did. You can even find one of my debug patches which implements it (but many > fancy hacks are missing). Cool. I did miss that. But if its' a TX descriptor issue it won't be due to a register access? :) Adrian -- 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
