On 11/04/2011 07:42 AM, Johannes Berg wrote:
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?
That seems feasible, though it still won't help with the valid ranges
for mpdu-density, for instance.
How about if I add some way to query this, but leave the code loose
in that it won't fail if someone tries to set a value that isn't
supported. That way, user-space can be lazy if it wants, but
can also get the details if it cares.
To get this info, I'm going to have to add a new driver API, as far
as I can tell, and I only have the ability to deal with ath9k, so
that will be the only driver that reports the mask. Of course,
others could modify their drivers as they wish.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
