linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Kalle Valo <kalle.valo@iki.fi>,
	Holger Schurig <holgerschurig@googlemail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ar9170 in AP mode
Date: Tue, 10 Nov 2009 11:39:02 +0100	[thread overview]
Message-ID: <1257849542.7037.42.camel@johannes.local> (raw)
In-Reply-To: <4AF88505.2060802@web.de>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

On Mon, 2009-11-09 at 22:09 +0100, Jan Kiszka wrote:

> Could someone briefly explain how the firmware is supposed to handle
> this case? By scanning outgoing frames for multicast addresses? Should
> the DTIM condition be detected and reported (via beacon) only by the
> firmware, or would the driver be involved to some degree? If we handle
> this transparently in the firmware, I guess that it would have to buffer
> not only a single multicast frame, right? Do we have enough memory for
> this on the chip?

The driver is always involved in some way, cf.
IEEE80211_TX_CTL_SEND_AFTER_DTIM and
IEEE80211_HW_HOST_BROADCAST_PS_BUFFERING in mac80211.h

As to what the right thing with ar9170 is -- I don't know. Maybe the
firmware could buffer a few frames, and the driver can push the
remaining frames down once the device tells it the beacon was sent. Or
maybe it's OK, although not perfect, if we simply send the frames once
the device says the beacon was sent... I've never understood how the QoS
implementation in this thing works, and that's kinda related.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-11-10 10:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 13:29 ar9170 in AP mode Jan Kiszka
2009-11-08 13:38 ` Kalle Valo
2009-11-08 13:47   ` Jan Kiszka
2009-11-08 14:01     ` Johannes Berg
2009-11-08 14:40       ` Jan Kiszka
2009-11-08 14:56         ` Johannes Berg
2009-11-09  8:16     ` Holger Schurig
2009-11-09  8:37       ` Kalle Valo
2009-11-09 14:14         ` John W. Linville
2009-11-09 21:09           ` Jan Kiszka
2009-11-10 10:39             ` Johannes Berg [this message]
2009-11-09 18:52         ` Jeffrey Baker
2009-11-09 19:49           ` Luis R. Rodriguez

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=1257849542.7037.42.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=holgerschurig@googlemail.com \
    --cc=jan.kiszka@web.de \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).