From: "Rami Rosen" <ramirose@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
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: Thu, 27 Nov 2008 11:31:08 +0200 [thread overview]
Message-ID: <eb3ff54b0811270131k7348b031j642fde5219ace758@mail.gmail.com> (raw)
In-Reply-To: <1227776790.3809.5.camel@johannes.berg>
Hello,
- Thanks a lot for this info!
- I will adjust my patch accordingly and preform tests to see that
multicast buffering works properly.
Regards,
Rami Rosen
On Thu, Nov 27, 2008 at 11:06 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2008-11-24 at 13:38 +0200, Rami Rosen wrote:
>> Hello,
>> I indeed intend to fix the driver to do the buffering and use
>> _get_buffered_bc() (and also add sequence numbering, which is easier).
>
> Sequence numbers are provided by the firmware, I think? At least beacons
> do have sequence numbers.
>
> Anyway, so I got some information, to fix this use _get_buffered_bc()
> when in zd_process_intr you get INT_CFG_NEXT_BCN; but this indicates
> that the beacon has _just_ been sent so you need to use _get_beacon()
> *after* _get_buffered_bc().
>
> johannes
>
prev parent reply other threads:[~2008-11-27 9:31 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
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 [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=eb3ff54b0811270131k7348b031j642fde5219ace758@mail.gmail.com \
--to=ramirose@gmail.com \
--cc=dsd@gentoo.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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