linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org, Luciano Coelho <coelho@ti.com>
Subject: Re: [PATCH 1/2] mac80211: allow low level drivers to report packet loss
Date: Wed, 20 Apr 2011 10:08:53 +0200	[thread overview]
Message-ID: <1303286933.3619.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <BANLkTik81g3NOwHcQk2eqOcMjaubCLdk+w@mail.gmail.com>

On Wed, 2011-04-20 at 00:54 +0300, Arik Nemtsov wrote:

> > That's your choice, but I wouldn't do it. You'll have to support TX
> > status when requested, otherwise AP operation won't work, so you need
> > the code anyway.
> 
> Can you elaborate why?
> 
> I'm assuming you mean the removal of
> IEEE80211_HW_REPORTS_TX_ACK_STATUS (in the second patch of this
> series). Note that it was only added recently, and AP/STA modes seemed
> to work fine without it.
> From a look in the code it seems this flag helps with connection
> monitoring in STA mode. The other use is determining the current PS
> mode when IEEE80211_HW_PS_NULLFUNC_STACK is enabled. These two are
> done by HW in wl12xx cards.

Well, there's the flag saying "you can rely on it", but there's also the
fact that AP mode relies on status for (some) frames anyway. So if you
just want to remove the flag I guess that's OK, but if you want to
remove all status processing .. that'll cause issues with AP mode.

johannes


  reply	other threads:[~2011-04-20  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 11:22 [PATCH 1/2] mac80211: allow low level drivers to report packet loss Arik Nemtsov
2011-04-18 11:22 ` [PATCH 2/2] wl12xx: support FW TX inactivity triggers Arik Nemtsov
2011-04-26  5:02   ` Arik Nemtsov
2011-04-18 12:26 ` [PATCH 1/2] mac80211: allow low level drivers to report packet loss Johannes Berg
2011-04-18 20:44   ` Arik Nemtsov
2011-04-19 12:36     ` Johannes Berg
2011-04-19 21:54       ` Arik Nemtsov
2011-04-20  8:08         ` Johannes Berg [this message]
2011-04-26 19:12           ` John W. Linville
2011-04-26 19:35             ` Arik Nemtsov

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=1303286933.3619.0.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arik@wizery.com \
    --cc=coelho@ti.com \
    --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).