From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211-wip preview
Date: Thu, 02 Aug 2012 08:49:10 -0700 [thread overview]
Message-ID: <501AA176.2050704@candelatech.com> (raw)
In-Reply-To: <1343922290.4471.21.camel@jlt3.sipsolutions.net>
On 08/02/2012 08:44 AM, Johannes Berg wrote:
> Hi,
>
> This is a more tentative preview, things are still subject to change.
>
> The included patchsets and their status:
> * P2P Device work
> I posted this, I'll apply it when I get back unless I see any
> objections then :-)
> * some more cleanups, including the CSA cleanups
> I posted most of these I believe, and will also apply most of it when
> I get back
> * a brcmsmac patch that I posted -- I'm not going to apply it but I
> just wanted to do a random cleanup (the obsolete functions removal)
> * and channel context code of course!
> This is still WIP, I need to
> - address SMPS -- I might just do passive/active # of chains per
> channel context and let the driver sort out the rest, this gives it
> more information and flexibility
> - TX power -- I'm open to suggestions about how we should do this,
> technically the user setting could be per virtual interface, but do
> we care? I have a feeling it should be per channel since even 11h
> TX power reduction is defined for the entire channel
I would love for tx power to be per network device. If nothing else,
one could have two station interfaces talking on the same channel, to two different
APs..one close by and one far away. Could set the tx-power higher for
the far-away one, for example.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-08-02 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 15:44 mac80211-wip preview Johannes Berg
2012-08-02 15:49 ` Ben Greear [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=501AA176.2050704@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).