From: Dennis H Jensen <dennis.h.jensen@siemens.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: fix channel to frequency mapping in 5.9GHz range
Date: Tue, 15 Oct 2013 11:40:12 +0200 [thread overview]
Message-ID: <1381830012.3711.50.camel@djensen-laptop> (raw)
In-Reply-To: <1381763193.13092.19.camel@jlt4.sipsolutions.net>
On Mon, 2013-10-14 at 17:06 +0200, Johannes Berg wrote:
> On Mon, 2013-10-14 at 16:58 +0200, Dennis H Jensen wrote:
>
> > > > The commit 59eb21a6504731fc16db4cf9463065dd61093e08 moved those channels
> > > > to 4.9 GHz but left a hole in the 5.9 Ghz range.
> > >
> > > But there was no +/- 15 before, so what gives?
> >
> > Well no :) but there also wasn't a special case for that particular
> > channel set (182 - 196).
>
> Yes, but then before 5910 would have been channel 182. Now you're making
> it channel 197. That doesn't really make sense at all.
OK, fair enough, but the fact is that there is a hole in the frequencies
that were added in 802.11p.
> > In case that doesn't do it. What is needed to get channel 182 to be 5910
> > MHz as Annex E defines for the US and Europe? Channel to frequency
> > mapping based on operating class?
>
> Annex E is the 802.11 spec, to get something into that ...
You misunderstood me; the European operating class 14, for example,
states that channel 182 is to be 5910.
Best regards,
Dennis
next prev parent reply other threads:[~2013-10-15 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:59 [PATCH] cfg80211: fix channel to frequency mapping in 5.9GHz range Dennis H Jensen
2013-10-11 13:56 ` Johannes Berg
2013-10-11 15:45 ` Dennis H Jensen
2013-10-14 12:02 ` Johannes Berg
2013-10-14 12:16 ` Dennis H Jensen
2013-10-14 14:02 ` Johannes Berg
2013-10-14 14:58 ` Dennis H Jensen
2013-10-14 15:06 ` Johannes Berg
2013-10-15 9:40 ` Dennis H Jensen [this message]
2013-10-17 14:33 ` Johannes Berg
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=1381830012.3711.50.camel@djensen-laptop \
--to=dennis.h.jensen@siemens.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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