On Wed, 2007-12-05 at 15:05 -0800, Jean Tourrilhes wrote: > On Wed, Dec 05, 2007 at 05:44:32PM -0500, Dan Williams wrote: > > > > > > The problem is that there isn't a nice, generic capabilities field in > > > > WEXT. So we have to abuse an existing one, and I picked enc_capa. > > > > > > Please don't do that. It's fairly trivial to add a new field > > > in iwrange. And it's not like the sky will fall down if we add a field > > > in iwrange. If you want to do it, please do it right. > > > > Well, the problem I had with this is that it's less likely to get > > backported because it potentially breaks binary compatibility for > > distros. There are 3 options here: > > > > 1) overload enc_capa > > > > 2) add a field and start doing comparisons of the size of the iw_range > > structure to figure out what is available and what's not > > > > 3) Bump the WEXT version > > > > #3 is a non-starter because it is a much larger, more invasive change > > and requires more breakage of ABI and such. > > Hu ? Please tell me what will break. We can bump the WEXT > version pretty much any time we want, no userspace will fail. THe > worse you may see is an anoying warning message. It's a problem for backporting this fix to older kernels that are not 2.6.25. If a WEXT version bump is required, then you have two options to backport this to drivers: 1) take the entire driver as-is. This usually won't work because many drivers are in a lot of flux, especially the softmac ones with their interdependencies on the stack. 2) Backport the SCAN_CAPA stuff only and bump the wext version. This may mean that the driver says it supports WEXT 24 for example, but doesn't actually have all the features that the current kernel driver that advertises v24 has. Another dead end. > > I guess #2 is acceptable. > > Option 4 : use two flags (as described below), that way you > know if iwrange implement the feature or not. > > > > Note that there is one gotcha because of the state of > > > userspace, so if you want I can produce a kernel patch that will work > > > properly, and I'll add the usespace support for it as well. > > > > Could you describe that more? > > The iwrange in userspace has a few more stuff defined, so you > need to make sure to include padding to not add your field on an > already existing field. Check the wireless.21.h file. > Note that if you sign the usual suspects on that change, I'll > do the patch for you. > > > > That won't work. You have a tri-state, and with only a single > > > bit you can encode only two state. You basically have : > > > o driver that support ap_scan=1 > > > o driver that do not support ap_scan=1 > > > o driver that have not been updated or reside in old kernels > > > > Well, to be fair, the patch posted handles this perfectly well, because > > older kernels with drivers that don't have the capability just dont' > > advertise it. Therefore everything works fine. > > > > > So, at the minimum, you'd want : > > > ------------------------------------- > > > +#define IW_ENC_CAPA_SPECIFIC_SSID_SCAN 0x00000010 > > > +#define IW_ENC_CAPA_ANY_SSID_SCAN 0x00000020 > > > ------------------------------------- > > > > I'm not sure why we'd want ANY_SSID_SCAN? > > To distinguish driver that have not been updated or driver in > order kernel from drivers that do not support ap_scan=1. You may want > to do things slightly differently between those two. > It just act as : yes this driver has been audited and fixed to > export proper scanning capability support. So is the ANY_SSID_SCAN thing different from just calling SIOCSIWSCAN _without_ any options? I was under the impression that just calling SIWSCAN would scan for all SSIDs. I've actually thought about your proposal, and decided that you're right. I'll post another patch for more comments. dan - 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
