All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trying to set tx power (using txpower option)
Date: Fri, 8 Oct 2010 09:52:32 -0700	[thread overview]
Message-ID: <20101008165232.GI10149@tux> (raw)
In-Reply-To: <4CAF4B70.9050001@candelatech.com>

On Fri, Oct 08, 2010 at 09:48:48AM -0700, Ben Greear wrote:
> On 10/08/2010 09:45 AM, Luis R. Rodriguez wrote:
> > On Fri, Oct 8, 2010 at 9:23 AM, At Santos<atsan@hotmail.co.uk>  wrote:
> >>
> >>
> >>> Actually, you can set tx power with iw now:
> >>>
> >>> http://wireless.kernel.org/en/users/Documentation/iw#Setting_TX_power
> >>>
> >>> I will note you will need 2.6.36, or compat-wireless-2.6.36, otherwise
> >>> you have to use iwconfig, setting txpower with nl80211 was only added
> >>> as of 2.6.36.
> >>>
> >>> Luis
> >>
> >> Thanks for the response.
> >>
> >> I'm running with compat-wireless-2.6.36-rc3-1 and I'm finding that iw
> >> doesn't work with fixed or limit:
> >>
> >> $ sudo iw wlan0 set txpower fixed 20
> >> command failed: Operation not supported (-95)
> >>
> >> So it seems it's broken at the moment.
> >> To where should I report the bug?
> >
> > You can use bugzilla.kernel.org please report it there and we can fix
> > it. I can't look into right now though as I'm looking into another
> > issue. If someone else has cycles it would be appreciated.
> 
> I might be able to work on this,

awesome, thanks!

> in wireless-testing tree at least.

All development is assumed to take places on wireless-testing.git anyway, and
to send a fix for older kernels we first must address it there so indeed
its always the right place to do development, even for stable.

  Luis

WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	ath9k <ath9k-devel@venema.h4ckr.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] trying to set tx power (using txpower option)
Date: Fri, 8 Oct 2010 09:52:32 -0700	[thread overview]
Message-ID: <20101008165232.GI10149@tux> (raw)
In-Reply-To: <4CAF4B70.9050001@candelatech.com>

On Fri, Oct 08, 2010 at 09:48:48AM -0700, Ben Greear wrote:
> On 10/08/2010 09:45 AM, Luis R. Rodriguez wrote:
> > On Fri, Oct 8, 2010 at 9:23 AM, At Santos<atsan@hotmail.co.uk>  wrote:
> >>
> >>
> >>> Actually, you can set tx power with iw now:
> >>>
> >>> http://wireless.kernel.org/en/users/Documentation/iw#Setting_TX_power
> >>>
> >>> I will note you will need 2.6.36, or compat-wireless-2.6.36, otherwise
> >>> you have to use iwconfig, setting txpower with nl80211 was only added
> >>> as of 2.6.36.
> >>>
> >>> Luis
> >>
> >> Thanks for the response.
> >>
> >> I'm running with compat-wireless-2.6.36-rc3-1 and I'm finding that iw
> >> doesn't work with fixed or limit:
> >>
> >> $ sudo iw wlan0 set txpower fixed 20
> >> command failed: Operation not supported (-95)
> >>
> >> So it seems it's broken at the moment.
> >> To where should I report the bug?
> >
> > You can use bugzilla.kernel.org please report it there and we can fix
> > it. I can't look into right now though as I'm looking into another
> > issue. If someone else has cycles it would be appreciated.
> 
> I might be able to work on this,

awesome, thanks!

> in wireless-testing tree at least.

All development is assumed to take places on wireless-testing.git anyway, and
to send a fix for older kernels we first must address it there so indeed
its always the right place to do development, even for stable.

  Luis

  reply	other threads:[~2010-10-08 16:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 12:04 [ath9k-devel] trying to set tx power (using txpower option) At Santos
2010-10-08  9:46 ` At Santos
2010-10-08 11:12   ` Peter Stuge
2010-10-08 15:27     ` Luis R. Rodriguez
2010-10-08 16:23       ` At Santos
2010-10-08 16:45         ` Luis R. Rodriguez
2010-10-08 16:45           ` Luis R. Rodriguez
2010-10-08 16:48           ` Ben Greear
2010-10-08 16:48             ` Ben Greear
2010-10-08 16:52             ` Luis R. Rodriguez [this message]
2010-10-08 16:52               ` Luis R. Rodriguez
2010-10-08 17:07               ` Ben Greear
2010-10-08 17:07                 ` Ben Greear
2010-10-08 17:12                 ` Johannes Berg
2010-10-08 17:12                   ` Johannes Berg
2010-10-08 17:24                   ` Ben Greear
2010-10-08 17:24                     ` Ben Greear
2010-10-08 17:28                     ` Johannes Berg
2010-10-08 17:28                       ` Johannes Berg
2010-10-08 17:38                       ` Ben Greear
2010-10-08 17:38                         ` Ben Greear
2010-10-08 17:41                     ` David Lamparter
2010-10-08 17:41                       ` David Lamparter
2010-10-08 18:00                       ` David Willmore
2010-10-08 18:00                         ` David Willmore
2010-10-08 18:05                         ` Johannes Berg
2010-10-08 18:05                           ` Johannes Berg
2010-10-08 23:10                           ` David Willmore
2010-10-08 23:10                             ` David Willmore

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=20101008165232.GI10149@tux \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.