Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Does ath9k support beam forming?
Date: Wed, 29 Aug 2012 07:59:50 -0700	[thread overview]
Message-ID: <503E2E66.8010909@candelatech.com> (raw)
In-Reply-To: <CAD2nsn2JFEAwB0AauFiEYxj=mC7dNjFZn12EQ0q-aOwXjfZj4A@mail.gmail.com>

On 08/28/2012 10:05 PM, Mohammed Shafi wrote:
> Hi Ben,
>
> On Wed, Aug 29, 2012 at 12:29 AM, Ben Greear <greearb@candelatech.com> wrote:
>> I saw some RFC patches about beam-forming from 2010, but grepping current
>> code doesn't find anything that indicates these patches ever made it
>> upstream.
>> Of course, I could be looking for the wrong thing...
>
> i think even though the patches are ready for submission,
> I think the testing them proved to be very challenging, where there
> does not seems to be consistent improvement(if not decrease)
> in throughput.  I can be wrong.
>
>>
>> Does the current ath9k code support beam-forming?
>
> no. hopefully we can support them(yet we need some considerable
> amount of time to test  i suppose).

Can you post the latest patch series for this?

And maybe we can make the functionality configurable by debugfs
so that we can test it out easily?

Are there any particular test cases that would help verify the
patches?

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

       reply	other threads:[~2012-08-29 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <503D14FF.5000309@candelatech.com>
     [not found] ` <CAD2nsn2JFEAwB0AauFiEYxj=mC7dNjFZn12EQ0q-aOwXjfZj4A@mail.gmail.com>
2012-08-29 14:59   ` Ben Greear [this message]
     [not found]     ` <CAD2nsn3jzWn+pW_3ZQEPtzHRwtZNy_k6=5WtB+F-J-vuMTvyKw@mail.gmail.com>
2012-08-31 15:02       ` [ath9k-devel] Does ath9k support beam forming? Ben Greear

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=503E2E66.8010909@candelatech.com \
    --to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox