linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kalle.valo@iki.fi>,
	Vivek Natarajan <vivek.natraj@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Always send a null data frame if TIM bit is  set.
Date: Thu, 2 Apr 2009 19:30:04 +0200	[thread overview]
Message-ID: <200904021930.06031.IvDoorn@gmail.com> (raw)
In-Reply-To: <1238666571.4141.14.camel@johannes.local>

On Thursday 02 April 2009, Johannes Berg wrote:
> On Thu, 2009-04-02 at 08:52 +0300, Kalle Valo wrote:
> 
> > I really would like to have some frame ack callback to mac80211, even
> > not all drivers support that. Otherwise we cannot reliably go to power
> > save because the AP might not receive our nullfunc frame. I have to
> > think about this and I'll try to propose something later on.
> 
> I suppose we could well assume that we do get TX status for those
> devices that do support power save -- which devices would that affect?

rt2500usb and rt73usb don't provide a valid TX status but do support
power save at he moment. I have to add that I'm in contact with somebody
who is looking into supporting Ack-based TX status reporting in mac80211
which could cure this problem. I have directed him to the linux-wireless list
so he will probably soon send his ideas to the list.

In any case, for now we can assume rt2500usb and rt73usb to be a problem.

Ivo

      reply	other threads:[~2009-04-02 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 14:50 [PATCH] mac80211: Always send a null data frame if TIM bit is set Vivek Natarajan
2009-03-04 10:55 ` Kalle Valo
2009-04-01  4:15 ` Vivek Natarajan
2009-04-02  5:52   ` Kalle Valo
2009-04-02 10:02     ` Johannes Berg
2009-04-02 17:30       ` Ivo van Doorn [this message]

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=200904021930.06031.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vivek.natraj@gmail.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 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).