From: Bruno Randolf <br1@einfach.org>
To: Brian Prodoehl <bprodoehl@gmail.com>
Cc: johannes@sipsolutions.net, linville@tuxdriver.com,
gwingerde@gmail.com, dcbw@redhat.com,
linux-wireless@vger.kernel.org, mcgrof@gmail.com
Subject: Re: [PATCH 2] cfg80211: Extend channel to frequency mapping for 802.11j
Date: Tue, 18 Jan 2011 11:50:15 +0900 [thread overview]
Message-ID: <201101181150.15936.br1@einfach.org> (raw)
In-Reply-To: <AANLkTi=SbkiZE0-5bJ+jraMhCMbvyaF=L0HOq5o0LtyJ@mail.gmail.com>
On Tue January 18 2011 11:42:49 Brian Prodoehl wrote:
> On Mon, Jan 17, 2011 at 8:06 PM, Bruno Randolf <br1@einfach.org> wrote:
> > On Tue January 18 2011 05:17:31 Brian Prodoehl wrote:
> >> Yeah, looks good. Is it worth noting that none of the drivers
> >> actually support the 802.11j channels yet?
> >
> > I am already using it locally in ath5k. I have it working in 4.9GHz, but
> > i'm not exactly sure in which cases i can enable the 4.9GHz channels. I
> > will send patches after the mac80211 part got merged.
>
> I have it working in ath9k, as well.
Good to hear. Do you have any information on when we can enable these
frequencies? I'm not sure all cards are calibrated for 4.9GHz. Any info about
this from Atheros, Luis?
> iw needs the same tweak to
> ieee80211_channel_to_frequency. Where do patches to iw get submitted?
I was waiting with positng the iw part until the mac80211 patch is accepted
and merged. It should also posted on this list and cc johannes.
bruno
next prev parent reply other threads:[~2011-01-18 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 4:37 [PATCH 2] cfg80211: Extend channel to frequency mapping for 802.11j Bruno Randolf
2011-01-17 20:17 ` Brian Prodoehl
2011-01-18 1:06 ` Bruno Randolf
2011-01-18 2:42 ` Brian Prodoehl
2011-01-18 2:50 ` Bruno Randolf [this message]
2011-01-21 12:16 ` Luciano Coelho
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=201101181150.15936.br1@einfach.org \
--to=br1@einfach.org \
--cc=bprodoehl@gmail.com \
--cc=dcbw@redhat.com \
--cc=gwingerde@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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 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).