On Mon, Oct 15, 2007 at 05:57:11PM -0700, Jean Tourrilhes wrote: > On Tue, Sep 11, 2007 at 06:07:53PM +0200, Johannes Berg wrote: > > Hi Jean, > > Hi again, > > > Anyhow, the problem is that my landlord has an AP that broadcasts an > > SSID with a 0xFC byte in it (supposedly an "ü" in windows). iwlist, > > however, just prints > > > > ESSID:"B > > You remember that problem ? Well, we now have a new version of > Wireless Tools that support that. However, this is blocked because the > necessary kernel patch has not gone yet in the kernel. > I've sent the patch to John twice, with you in cc for the last > occurence. It seems that John for some reason does not receive e-mail > from me, or something else. This was the last time : > http://marc.info/?l=linux-wireless&m=119022849315111&w=2 > So, would you mind pushing yourself this patch to John ? > Thanks in advance... > > Jean > > Signed-off-by: Jean Tourrilhes <jt@xxxxxxxxxx> Jean, you can keep whining and complaining. But you never address the issue of preserving the userland ABI. Simply releasing a new, smarter, better wireless-tools does not change the situation. Because of the confusion in SSID handling when WEXT was defined, WEXT is just never going to support a 32-byte SSID unless it happens to end in a NULL. Sorry. I don't see how the patch you wish to revert has anything to do with the umlaut issue. If it does, please explain how or feel free to propose a patch that corrects it while still preserving the userland ABI. John P.S. Please note that the userland ABI concern is not some pet issue for me. This comes from the community at large, including Linus, Jeff Garzik, and other notable contributors. -- John W. Linville linville@xxxxxxxxxxxxx - 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
