From: Johannes Berg <johannes@sipsolutions.net>
To: Rami Rosen <ramirose@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org, j@w1.fi,
Daniel Drake <dsd@gentoo.org>
Subject: Re: [PATCH 2/2] zd1211rw: enable an AP that can't support fully PS clients (wireless-testing).
Date: Mon, 24 Nov 2008 12:21:34 +0100 [thread overview]
Message-ID: <1227525694.3599.95.camel@johannes.berg> (raw)
In-Reply-To: <eb3ff54b0811240309u31944469xa444ee25f8ac8496@mail.gmail.com> (sfid-20081124_120908_115398_E83F0212)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Mon, 2008-11-24 at 13:09 +0200, Rami Rosen wrote:
> If you are talking about whether the zd1211 driver can buffer
> mcast/bcast frames in software, it seems to me that the answer is
> negative, since there is no call for ieee80211_get_buffered_bc() in
> the zd1211rw driver code and also there is no handling of
> IEEE80211_TX_CTL_SEND_AFTER_DTIM or
> IEEE80211_HW_HOST_BROADCAST_PS_BUFFERING in the zd1211rw driver code.
> This what made me add the NL80211_ATTR_WIPHY_AP_PS_CHALLENGED
> attribute and prepare this patch.
Yes, I know that's why you did it, but I'm still wondering whether it
was necessary, is it really impossible to implement mcast/bcast
buffering with this hardware? IOW, can we fix the driver to do the
buffering and using _get_buffered_bc()?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-24 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 7:44 [PATCH 2/2] zd1211rw: enable an AP that can't support fully PS clients (wireless-testing) Rami Rosen
2008-11-24 10:35 ` Johannes Berg
2008-11-24 11:09 ` Rami Rosen
2008-11-24 11:21 ` Johannes Berg [this message]
2008-11-24 11:38 ` Rami Rosen
2008-11-24 11:44 ` Johannes Berg
2008-11-27 9:06 ` Johannes Berg
2008-11-27 9:31 ` Rami Rosen
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=1227525694.3599.95.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dsd@gentoo.org \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ramirose@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