From: Johannes Berg <johannes@sipsolutions.net>
To: Dennis H Jensen <dennis.h.jensen@siemens.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: fix channel to frequency mapping in 5.9GHz range
Date: Mon, 14 Oct 2013 16:02:50 +0200 [thread overview]
Message-ID: <1381759370.13092.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1381752976.3711.14.camel@djensen-laptop>
On Mon, 2013-10-14 at 14:16 +0200, Dennis H Jensen wrote:
> On Mon, 2013-10-14 at 14:02 +0200, Johannes Berg wrote:
> > On Fri, 2013-10-11 at 17:45 +0200, Dennis H Jensen wrote:
> >
> > > > > + else if (chan > 196)
> > > > > + return 5000 + (chan - 15) * 5;
> > > >
> > > > Where does the +/- 15 come from? I can't find any evidence for this in
> > > > Annex E.
> > >
> > > I didn't double check Annex E. I just wanted to recover the lost
> > > frequencies that the 15 channels (182 - 196), map into 4.9 GHz.
> >
> > "Recover"? When did they work? What broke them?
>
> 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?
johannes
next prev parent reply other threads:[~2013-10-14 14:03 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 [this message]
2013-10-14 14:58 ` Dennis H Jensen
2013-10-14 15:06 ` Johannes Berg
2013-10-15 9:40 ` Dennis H Jensen
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=1381759370.13092.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dennis.h.jensen@siemens.com \
--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;
as well as URLs for NNTP newsgroup(s).