From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Masakazu Mokuno <mokuno@sm.sony.co.jp>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, cbe-oss-dev@ozlabs.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Stefan Assmann <sassmann@suse.de>
Subject: Re: [PATCH] PS3: gelic: ignore scan info from zero SSID beacons
Date: Tue, 11 Mar 2008 12:50:37 -0400 [thread overview]
Message-ID: <1205254237.8774.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1205252287.6387.54.camel@johannes.berg>
On Tue, 2008-03-11 at 17:18 +0100, Johannes Berg wrote:
> On Tue, 2008-03-11 at 13:15 +0900, Masakazu Mokuno wrote:
> > Some implementations of the hidden SSID APs emit beacons which have the zero
> > length SSID information element instead of SSID padded by null (\0) characters.
> > If the firmware of the PS3 wireless hardware meets these beacons, it abandons parsing
> > IEs. Thus guest OSes get the invalid scan information for the AP.
> >
> > To work around this, ignore these scan informations from the list.
>
> I'm not sure this is a good idea. Is there any way to get at decent
> information from those beacons?
Yeah, there are quite a few of these out there. Ideally the firmware
wouldn't puke on it...
Dan
next prev parent reply other threads:[~2008-03-11 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:15 [PATCH] PS3: gelic: ignore scan info from zero SSID beacons Masakazu Mokuno
2008-03-11 16:18 ` Johannes Berg
2008-03-11 16:50 ` Dan Williams [this message]
2008-03-11 17:10 ` John W. Linville
2008-03-12 2:18 ` Masakazu Mokuno
2008-03-12 8:25 ` Johannes Berg
2008-03-12 10:26 ` Masakazu Mokuno
2008-03-12 13:42 ` Dan Williams
2008-03-12 14:31 ` Johannes Berg
2008-03-12 14:43 ` Johannes Berg
2008-03-13 7:01 ` Masakazu Mokuno
2008-03-12 2:24 ` Masakazu Mokuno
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=1205254237.8774.0.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mokuno@sm.sony.co.jp \
--cc=sassmann@suse.de \
/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