From: "John W. Linville" <linville@tuxdriver.com>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Dan Williams <dcbw@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlist and network-manager bug report
Date: Tue, 16 Oct 2007 12:58:03 -0400 [thread overview]
Message-ID: <20071016165803.GA5677@tuxdriver.com> (raw)
In-Reply-To: <20071016005711.GA10957@bougret.hpl.hp.com>
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,
>=20
> Hi again,
>=20
> > Anyhow, the problem is that my landlord has an AP that broadcasts a=
n
> > SSID with a 0xFC byte in it (supposedly an "=FC" in windows). iwlis=
t,
> > however, just prints
> >=20
> > ESSID:"B
>=20
> You remember that problem ? Well, we now have a new version of
> Wireless Tools that support that. However, this is blocked because th=
e
> 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=3Dlinux-wireless&m=3D119022849315111&w=3D2
> So, would you mind pushing yourself this patch to John ?
> Thanks in advance...
>=20
> Jean
>=20
> Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
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.
--=20
John W. Linville
linville@tuxdriver.com
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-16 17:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 16:07 iwlist and network-manager bug report Johannes Berg
2007-09-12 15:22 ` Dan Williams
2007-09-12 17:01 ` Jean Tourrilhes
2007-09-13 7:11 ` Johannes Berg
2007-09-13 18:18 ` Johannes Berg
2007-09-14 18:09 ` Dan Williams
2007-09-14 18:25 ` Johannes Berg
2007-09-14 18:33 ` Dan Williams
2007-09-14 18:39 ` Johannes Berg
2007-09-14 19:12 ` dragoran
2007-09-14 20:05 ` Dan Williams
2007-09-14 20:10 ` dragoran
2007-09-18 0:36 ` Jean Tourrilhes
2007-09-18 10:15 ` Johannes Berg
2007-09-18 17:37 ` Jean Tourrilhes
2007-09-18 19:02 ` Dan Williams
2007-10-16 0:57 ` Jean Tourrilhes
2007-10-16 16:58 ` John W. Linville [this message]
2007-10-16 17:29 ` Jean Tourrilhes
2007-10-16 17:39 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016165803.GA5677@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).