On Thu, 2011-05-12 at 20:08 +0200, BjÃrn Smedman wrote: > > That has a failure path, and recently I posted a patch to advertise the > > interface type combinations. I don't think MAC addresses impose any sort > > of restriction. > > I think at least some rt2x00 hw may not be able to handle all > combinations of multi-vif MAC addresses. > > If I understand correctly ath9k will happily configure the hardware to > ack all BSSIDs if multi-vif MAC addresses are poorly chosen. I don't > know if that's a reason to fail but it wouldn't be good, right? That'd be possible I guess if you configure them so their XOR is all ones, but it doesn't matter -- you can fail that right now. Also, if the user configures it like that maybe that's their fault? > Another case where cross-vif constraints are difficult to handle is > BSS_CHANGED_ERP_SLOT / BSS_CHANGED_ERP_PREAMBLE. Again, I'm not sure > failing is the right way to handle this but at least ath9k seems > incapable of having separate slot times / preambles for separate > vifs... That's hard to believe since it's rate control stuff? johannes -- 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
