On Thu, 2011-11-03 at 11:17 -0700, Ben Greear wrote: > So back to the capabilities flag like I added in the -v2 patch? > Do you want one flag for each thing (set-mcs, disable-ht, > disable-ht40, set-mpdu, set-msdu), or maybe one flag for all of > this: set-ht-cap I think maybe a single one would be sufficient, but you'd still have no way of knowing what is actually supported for changing. Maybe you could advertise an ht_mask of things that can be changed? > My opinion remains that we should silently ignore un-supported > values..this way user-space works with the same config on old and new > kernels. In future patches, we can report the actual settings via > netlink or similar. > > But, I can add logic in user-space to detect kernel versions and > such and deal with this. Then you also wouldn't have to muck around with kernel version detection etc. you could just query the mask of things that can be changed. 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
