From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Mahesh <maheshp@posedge.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Chakra Parvathaneni <chakra@posedge.com>
Subject: Re: [RFCv2] cfg80211: 80Mhz Bandwidth channel flags in 5Gig band
Date: Sat, 25 Feb 2012 22:30:24 +0100 [thread overview]
Message-ID: <1330205424.3509.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAJ-VmomfVCc0oQMjfwsrheC+Z2k3+-czo4F9GeeO=upHiHnQxg@mail.gmail.com> (sfid-20120225_202329_108179_7C3BAD32)
On Sat, 2012-02-25 at 11:22 -0800, Adrian Chadd wrote:
> .. and this doesn't yet address VHT160, which is part of the 11ac spec too.
>
> I think it's worth having a bit more of a total, overall architecture
> discussion about what 11ac support -should- look like before bits are
> comitted, so you don't have to go and change them later (and possibly
> break some internal company drivers whilst doing so.)
Not like I care about that at all ... we change things all the time and
break drivers in the process. Is it even feasible to have non-upstream
drivers on the current wireless stack? I'd think you'd have to dedicate
one person full time to following our mac80211 changes ;-)
> So - what else is likely needed for the upcoming 11ac standard?
Well so obviously we need things like VHT capability stuff (advertising,
in scans, in assoc, for AP/GO mode in station info). I suspect you're
talking only about the regulatory/channel stuff? Mostly I'm confused
about the split channel thing there but I suppose regulatory-wise it's
just like using two channels at the same time.
> Disclaimer: I'm speaking from my personal opinion rather than that of
> Qualcomm Atheros.
Does anyone here have an "official opinion"? I doubt it :)
johannes
next prev parent reply other threads:[~2012-02-25 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:51 [RFC] cfg80211: 80Mhz Bandwidth channel flags in 5Gig band Mahesh
2012-02-22 17:57 ` Johannes Berg
2012-02-22 18:57 ` Johannes Berg
2012-02-24 5:25 ` [RFCv2] " Mahesh
2012-02-24 5:43 ` Adrian Chadd
2012-02-24 5:48 ` Mahesh
2012-02-24 8:01 ` Johannes Berg
2012-02-24 7:55 ` Johannes Berg
2012-02-24 11:21 ` Mahesh
2012-02-25 19:22 ` Adrian Chadd
2012-02-25 21:30 ` Johannes Berg [this message]
[not found] ` <eab3dfdc8ebc87ec08ca64db9f237d90@posedge.com>
2012-04-03 12:06 ` 802.11ac support Johannes Berg
2012-04-03 12:11 ` Johannes Berg
2012-04-05 4:21 ` Mahesh
2012-04-05 14:06 ` 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=1330205424.3509.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=chakra@posedge.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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).