All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH 1/7] rt2800: use BBP_R1 for setting tx power
Date: Mon, 8 Oct 2012 11:15:24 +0200	[thread overview]
Message-ID: <20121008091523.GB2478@redhat.com> (raw)
In-Reply-To: <506F0A56.70900@01019freenet.de>

Hi

On Fri, Oct 05, 2012 at 06:27:02PM +0200, Andreas Hartmann wrote:
> I would like to test this patchset. Whereon should I pay (most)
> attention? What do you expect to be changed (or not) behaviour with 2.4
> GHz / 40 MHz?

Yes, all band 2.4GHz/5GHz and bandwitch 20MHz/40MHz combinations are 
touched by those patches. 

You can check if patches make anything better on long distance
performance if you want to.

Thanks
Stanislaw


  reply	other threads:[~2012-10-08  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 11:44 [PATCH 1/7] rt2800: use BBP_R1 for setting tx power Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 2/7] rt2800: limit TX_PWR_CFG_ values to 0xc Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 3/7] rt2800: compensate tx power also for non 11b rates on 2GHz Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 4/7] rt2800: use eeprom OFDM 6M TX power as criterion Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 5/7] rt2800: pass channel pointer to rt2800_config_txpower Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 6/7] rt2800: allow to reduce tx power on devices not exporting power limit Stanislaw Gruszka
2012-10-05 11:44 ` [PATCH 7/7] rt2800: comment tx power settings Stanislaw Gruszka
2012-10-05 16:27 ` [rt2x00-users] [PATCH 1/7] rt2800: use BBP_R1 for setting tx power Andreas Hartmann
2012-10-08  9:15   ` Stanislaw Gruszka [this message]
2012-10-13  6:47     ` Andreas Hartmann
2012-10-13  7:57       ` Stanislaw Gruszka
2012-10-13  9:42         ` Andreas Hartmann

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=20121008091523.GB2478@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=andihartmann@01019freenet.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=users@rt2x00.serialmonkey.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 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.