From: Michael Buesch <mb@bu3sch.de>
To: Kalle Valo <Kalle.Valo@iki.fi>
Cc: linux-wireless@vger.kernel.org, Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH 06/12] Add support for monitor mode
Date: Sun, 9 Mar 2008 18:39:15 +0100 [thread overview]
Message-ID: <200803091839.15514.mb@bu3sch.de> (raw)
In-Reply-To: <87ve3vyj21.fsf@litku.valot.fi>
On Sunday 09 March 2008 17:10:46 Kalle Valo wrote:
> Michael Buesch <mb@bu3sch.de> writes:
>
> >> +#define AT76_SUPPORTED_FILTERS FIF_PROMISC_IN_BSS
> >
> > See my recent patch to zd1211rw:
> > [PATCH] zd1211rw: Fix beacon filter flags thinko
> > I think this thinko also applies here.
> >
> > A driver does not support a flag, if it can _not_ _provide_
> > a specific frame. (so in case it always filters it)
> > Not the other way around. So if it always
> > provides a specific type of frames, it _does_ support the filter flag.
>
> Thanks for looking at this.
>
> I have to admit that I didn't undertstand the filter flags logic at
> that time, but I think I understand it now. I hope this is right:
>
>
> static void at76_op_configure_filter(struct ieee80211_hw *hw,
> unsigned int changed_flags,
> unsigned int *total_flags, int mc_count,
> struct dev_addr_list *mc_list)
> {
> struct at76_priv *priv = hw->priv;
>
> at76_dbg(DBG_MAC80211, "%s(): changed_flags=0x%08x "
> "total_flags=0x%08x mc_count=%d",
> __func__, changed_flags, *total_flags, mc_count);
>
> *total_flags &= FIF_PROMISC_IN_BSS;
So your driver can not pass control frames and beacons in normal operation
to the stack?
>
> if (changed_flags & FIF_PROMISC_IN_BSS) {
> /* FIXME: access to priv->promisc should be protected with
> * priv->mtx, but it's impossible because this function
> * needs to be atomic */
> priv->promisc = *total_flags & FIF_PROMISC_IN_BSS;
> queue_work(hw->workqueue, &priv->work_set_promisc);
> }
>
> }
>
>
--
Greetings Michael.
next prev parent reply other threads:[~2008-03-09 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 14:59 [PATCH 00/12] at76_usb mac80211 port Kalle Valo
2008-02-10 14:59 ` [PATCH 01/12] Use net/mac80211.h instead of net/ieee80211.h Kalle Valo
2008-02-10 15:00 ` [PATCH 02/12] Add at76_dbg_dump() macro Kalle Valo
2008-02-10 15:00 ` [PATCH 03/12] Convert DBG_TX levels to use at76_dbg_dump() Kalle Valo
2008-02-10 15:00 ` [PATCH 04/12] Add DBG_CMD for debugging firmware commands Kalle Valo
2008-02-10 15:00 ` [PATCH 05/12] at76_usb: add mac80211 support Kalle Valo
2008-02-10 15:00 ` [PATCH 06/12] Add support for monitor mode Kalle Valo
2008-02-10 15:49 ` Michael Buesch
2008-02-10 15:52 ` Michael Buesch
2008-03-09 16:10 ` Kalle Valo
2008-03-09 17:39 ` Michael Buesch [this message]
2008-02-10 15:00 ` [PATCH 07/12] Add support for WEP Kalle Valo
2008-02-10 15:00 ` [PATCH 08/12] Remove support the legacy stack Kalle Valo
2008-02-10 15:00 ` [PATCH 09/12] Use wiphy_name everywhere where needed Kalle Valo
2008-02-10 15:01 ` [PATCH 10/12] Allocate struct at76_priv using ieee80211_alloc_hw() Kalle Valo
2008-02-10 15:01 ` [PATCH 11/12] Prepare for struct net_device removal Kalle Valo
2008-02-10 15:01 ` [PATCH 12/12] Remove struct net_device Kalle Valo
2008-02-11 5:05 ` [PATCH 00/12] at76_usb mac80211 port Pavel Roskin
2008-02-11 5:17 ` Pavel Roskin
2008-03-09 16:43 ` Kalle Valo
2008-03-10 1:00 ` Pavel Roskin
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=200803091839.15514.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Kalle.Valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.