From: Bruno Randolf <br1@einfach.org>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: "ext Gabay, Benzy" <benzyg@ti.com>,
"luciano.coelho@nokia.com" <luciano.coelho@nokia.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] wl1271: Prevent ad-hoc and active scanning on 11a DFS frequencies
Date: Wed, 17 Nov 2010 18:57:20 +0900 [thread overview]
Message-ID: <201011171857.20200.br1@einfach.org> (raw)
In-Reply-To: <1289982876.2522.157.camel@wimaxnb.nmp.nokia.com>
On Wed November 17 2010 17:34:36 Juuso Oikarinen wrote:
> On Wed, 2010-11-17 at 02:25 -0600, ext Gabay, Benzy wrote:
> > Yet another question on this topic,
> > Ad-Hoc was designed originally for B mode only. Some companies extended
> > it to G also. Do we have MAC802.11 support for Ad-Hoc on 11a channels
> > these days?
>
> Based on our testing, ad-hoc on 11a appears to work, tested between two
> linux-based devices.
Sure, we're using it all day & night... :)
In the few bands where it's permitted, of course.
bruno
prev parent reply other threads:[~2010-11-17 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 10:27 [PATCH 1/2] wl1271: Prevent ad-hoc and active scanning on 11a DFS frequencies juuso.oikarinen
2010-11-10 10:27 ` [PATCH 2/2] Revert "wl1271: Change supported channel order for a more optimal scan" juuso.oikarinen
2010-11-10 11:18 ` Gery Kahn
2010-11-10 11:21 ` Juuso Oikarinen
2010-11-10 11:36 ` Gery Kahn
2010-11-10 11:42 ` Juuso Oikarinen
2010-11-11 19:47 ` Gery Kahn
2010-11-10 11:02 ` [PATCH 1/2] wl1271: Prevent ad-hoc and active scanning on 11a DFS frequencies Tuomas Katila
2010-11-11 9:35 ` Luciano Coelho
2010-11-11 12:15 ` Luciano Coelho
2010-11-17 6:52 ` Gabay, Benzy
2010-11-17 7:00 ` Juuso Oikarinen
2010-11-17 8:25 ` Gabay, Benzy
2010-11-17 8:34 ` Juuso Oikarinen
2010-11-17 9:57 ` Bruno Randolf [this message]
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=201011171857.20200.br1@einfach.org \
--to=br1@einfach.org \
--cc=benzyg@ti.com \
--cc=juuso.oikarinen@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.