On Tue, Oct 03, 2006 at 12:49:57PM -0700, Jean Tourrilhes wrote:
> No, it's not. But as soon as *some part* of WE-21 appears in
> the kernel, the userspace expect the ESSID change. If we want to have
> WE-21 without the ESSID change, we need to fix userspace.
Or leave WIRELESS_EXT at 20 and come up with a new way of versioning any
future changes in WE.. Yes, having two different mechanisms for version
number is ugly, but it could prevent userspace breakage.
(And based on the other messages in this thread, it might be useful to
include the userspace program's idea of the version in those new
commands to allow multiple interface versions to be supported by the
kernel).
--
Jouni Malinen PGP id EFC895FA
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]