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] Disabling Link-Layer Acks
Date: Fri, 2 Oct 2009 14:29:08 -0700	[thread overview]
Message-ID: <20091002212908.GD9121@mosca> (raw)
In-Reply-To: <d355d36c0910010950y59f1afe5qc4e78c312303e4b9@mail.gmail.com>

On Thu, Oct 01, 2009 at 09:50:47AM -0700, Matt Tierney wrote:
> This is bumping an old question <http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg00016.html> but I was wondering if there was a simple (quick and dirty, if need be) way to disable link-layer acks.
> 
> I think I found the right place to do this in the xmit.c code, under the setup_tx_flags function:
> 
>         if (tx_info->flags & IEEE80211_TX_CTL_NO_ACK)
>                 flags |= ATH9K_TXDESC_NOACK;
> 
> I expect that I would just need to comment out the first line with the if-condition.
> 
> Is this a correct way to handle disabling link-layer acks for now?

Not sure, I'd be checking the code just as you are but I will not another
thing you may want to look at also is the extremely well documented
ath_hw_setbssidmask():

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/hw.c;h=ecc9eb01f4fa12bddfd7ab044c79847bfe643c84;hb=HEAD

  Luis

  reply	other threads:[~2009-10-02 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 16:50 [ath9k-devel] Disabling Link-Layer Acks Matt Tierney
2009-10-02 21:29 ` Luis R. Rodriguez [this message]
2009-10-07  6:12 ` Sujith
2009-10-07 16:14   ` Valentin Manea
2009-10-07 17:11     ` Ranga Rao Ravuri
2009-10-07 17:16       ` Valentin Manea
  -- strict thread matches above, loose matches on Subject: below --
2008-07-29 14:16 [ath9k-devel] Disabling link-layer ACKs William Usher

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=20091002212908.GD9121@mosca \
    --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.