From: Kalle Valo <kalle.valo@nokia.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
linville@tuxdriver.com, yi.zhu@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: make listen_interval be configurable by low level driver
Date: Tue, 15 Jul 2008 22:35:29 +0300 [thread overview]
Message-ID: <87od4z9bzy.fsf@nokia.com> (raw)
In-Reply-To: <1ba2fa240807150129v4906b7bcyba66ab62b57c5d71@mail.gmail.com> (ext Tomas Winkler's message of "Tue\, 15 Jul 2008 11\:29\:50 +0300")
Tomas Winkler <tomasw@gmail.com> writes:
[listen interval]
> This value for iwlwifi hw is derived from maximal supported beacon
> interval and size of the internal HW timers. This value is hard
> coded in the driver.
Ok, now I understand a bit better. Yes, a value like that would be
good to deliver to mac80211.
Just out of curiosity, what's the current hard coded maximum value?
--
Kalle Valo
next prev parent reply other threads:[~2008-07-15 19:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 12:31 [PATCH 1/2] mac80211: pass dtim_period to low level driver Tomas Winkler
2008-07-14 12:31 ` [PATCH 2/2] mac80211: make listen_interval be configurable by " Tomas Winkler
2008-07-14 12:38 ` Johannes Berg
2008-07-14 12:46 ` Tomas Winkler
2008-07-14 13:26 ` Kalle Valo
2008-07-14 21:34 ` Tomas Winkler
2008-07-15 7:21 ` Kalle Valo
2008-07-15 7:30 ` Kalle Valo
2008-07-15 8:15 ` Johannes Berg
2008-07-15 8:13 ` Johannes Berg
2008-07-15 8:12 ` Johannes Berg
2008-07-15 8:29 ` Tomas Winkler
2008-07-15 8:41 ` Johannes Berg
2008-07-15 9:58 ` Helmut Schaa
2008-07-15 10:42 ` Tomas Winkler
2008-07-15 19:35 ` Kalle Valo [this message]
2008-07-15 19:30 ` Kalle Valo
2008-07-14 13:13 ` Kalle Valo
2008-07-14 12:36 ` [PATCH 1/2] mac80211: pass dtim_period to " Johannes Berg
2008-07-14 12:38 ` Tomas Winkler
2008-07-14 12:40 ` Johannes Berg
2008-07-14 13:17 ` Kalle Valo
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=87od4z9bzy.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).