From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 3/7] iwlwifi: fix priv->iw_mode setting when multiple vif are configured
Date: Fri, 07 Nov 2008 16:04:55 +0800 [thread overview]
Message-ID: <1226045096.2604.253.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1225967956.3619.199.camel@johannes.berg>
On Thu, 2008-11-06 at 18:39 +0800, Johannes Berg wrote:
> Ok, for one, it seems weird that you're saying you handled
> * other bss
> * allmulti
> * bcn/presp promisc
> * control
> without doing anything. Does your hw/fw really always pass up control
> frames? I didn't think it does.
>
> Also, it seems rather odd that you need to reconnect etc. when a monitor
> interface is added, that would destroy AP and mesh modes completely when
> somebody adds a new monitor interface on AP mode to see what's going on.
>
> Can you really not actually implement the filter flags but have to
> completely reprogram the firmware for monitor mode? What exactly does
> monitor mode do? It seems that at least, the logic in configure_filter
> should mask out the control/allmulti flags when otherbss is not set,
> because right now, if I add a monitor interface that _only_ asks for
> control frames and _not_ other bss frames, it doesn't look like it would
> work.
You are right. We don't need to reprogram the firmware completely to
support these filter flags. Will post a patch to reimplement our
configure_filter handler early next week.
Thanks,
-yi
prev parent reply other threads:[~2008-11-07 8:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 21:05 [PATCH 0/7] iwlwifi driver updates Reinette Chatre
2008-10-29 21:05 ` [PATCH 1/7] iwlwifi: reorganize flow handler bitology Reinette Chatre
2008-10-29 21:05 ` [PATCH 2/7] iwlwifi: trivial removal of some 4965 remaining from iwl-agn-rs.h Reinette Chatre
2008-10-29 21:05 ` [PATCH 3/7] iwlwifi: fix priv->iw_mode setting when multiple vif are configured Reinette Chatre
2008-10-29 21:05 ` [PATCH 4/7] iwlwifi: rename generic iwlagn functions that had a HW specific name Reinette Chatre
2008-10-29 21:05 ` [PATCH 5/7] iwlwifi: rename double inclusion protection name in iwl-commands.h Reinette Chatre
2008-10-29 21:05 ` [PATCH 6/7] iwlwifi: iwl-agn-rs: initialize rs with valid antenna Reinette Chatre
2008-10-29 21:05 ` [PATCH 7/7] iwlwifi: do not call statistics from rfkill Reinette Chatre
2008-10-30 9:18 ` [PATCH 3/7] iwlwifi: fix priv->iw_mode setting when multiple vif are configured Johannes Berg
2008-11-05 0:09 ` Zhu Yi
2008-11-05 11:27 ` Johannes Berg
2008-11-06 2:34 ` Zhu Yi
2008-11-06 10:39 ` Johannes Berg
2008-11-07 8:04 ` Zhu Yi [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=1226045096.2604.253.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@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).