From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: regulatory hiccup
Date: Tue, 27 Jul 2010 16:51:06 -0700 [thread overview]
Message-ID: <AANLkTinNAWZvDJVqL9U8AmJUNqV=fLLo4BN=dEfg=8cd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimZsj6+cp6YGoVFn06NEQR3ZBCAheaWHaKPZNK6@mail.gmail.com>
On Tue, Jul 27, 2010 at 4:46 PM, Andrew Lutomirski <luto@mit.edu> wrote:
> On Tue, Jul 27, 2010 at 7:33 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>>>
>>> AFAICT net/wireless/reg.c ignores the last bit, and the other APs that
>>> work correctly here don't send country IEs.
>>
>> Can you provide the output of iw dev wlan0 scan from a fresh git
>> version of iw? That will actually tell me more than your listing.
>
> Unfortunately (or fortunately, I suppose) I can't, because a firmware
> upgrade for the AP removed the country IE entirely. But if we're
> ignoring that data in 2.6.36 anyway, I'm not too worried. If you
> really want that data, I can downgrade the AP the week after next and
> get it.
>
> (FWIW, it looks like the Intel driver on Windows refused to work with
> that AP but other people with macbooks could use it just fine. I'd
> guess that no one would complain if Linux ignored country IEs that
> were transmitted outside their own "allowed" band, but this seems to
> be moot anyway.)
If sounds like the AP may have had an issue if the country IE is no
longer present and by the quick looks of your output it could have
been.. so unless you're confident of the AP I would think this is an
AP bug. If its a STA bug for sure though we certainly need to address
the issue on 2.6.35 even if 2.6.36 has a proper fix of ignoring the IE
altogether.
> P.S. My thread about the AP that works on 2.6.34 but can't associate
> most of the time on 2.6.35-rc6 is the same AP but with the new
> firmware.
Wonderful.
Luis
next prev parent reply other threads:[~2010-07-27 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 19:30 regulatory hiccup Andrew Lutomirski
2010-07-23 19:35 ` Andrew Lutomirski
2010-07-23 20:03 ` Andrew Lutomirski
2010-07-27 23:33 ` Luis R. Rodriguez
2010-07-27 23:46 ` Andrew Lutomirski
2010-07-27 23:51 ` Luis R. Rodriguez [this message]
2010-07-27 23:32 ` Luis R. Rodriguez
2010-07-27 23:30 ` Luis R. Rodriguez
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='AANLkTinNAWZvDJVqL9U8AmJUNqV=fLLo4BN=dEfg=8cd@mail.gmail.com' \
--to=mcgrof@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luto@mit.edu \
/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).