linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Bas Hulsken <bhulsken@hotmail.com>
Cc: Adam Baker <linux@baker-net.org.uk>, linux-wireless@vger.kernel.org
Subject: Re: rt2500pci, infinite calls to rt2x00mc_configure_filter
Date: Sun, 30 Mar 2008 15:27:34 +0200	[thread overview]
Message-ID: <200803301527.34583.IvDoorn@gmail.com> (raw)
In-Reply-To: <1206882945.4973.5.camel@Bas>

Hi,

> > Ivo,
> > Don't forget that there was no response to the request for someone to test
> > if broadcast packets were received in monitor mode on the older hardware
> > so if the filter flags don't select multicast traffic we could be losing
> > broadcast traffic too. I'm not sure if the stack will be reporting any
> > active multicast groups in AP mode. (For the benefit of others the only
> > reason normal broadcast traffic was working was because there was always a
> > multicast group present, Ivo's request is linked below.)
> > 
> > http://sourceforge.net/mailarchive/forum.php?thread_name=200803031921.41634.IvDoorn%40gmail.com&forum_name=rt2400-devel
> > 
> I would like to test for this, but I'm not quite sure how, I've read
> Ivo's original message, but I can't find the monitoring bug discussion
> Ivo is referring to. Would the frame captures on debugfs, again with the
> above mentioned tools test for this bug as well? Or is there something
> else I have to do?

So far I have received 1 result for the above test request which indicated rt2500pci
wasn't harmed with this bug. However, latest rt2x00 has Adam's patch active for
all rt2x00 drivers (since the code is now handled in rt2x00mac.c).
So this means that that multicast bug should have no influence for this bug.

Ivo

  reply	other threads:[~2008-03-30 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 14:34 rt2500pci, infinite calls to rt2x00mc_configure_filter Bas Hulsken
2008-03-29 14:53 ` Ivo van Doorn
2008-03-29 16:42   ` Bas Hulsken
2008-03-29 17:01     ` Ivo van Doorn
2008-03-29 23:45       ` Adam Baker
2008-03-30 13:15         ` Bas Hulsken
2008-03-30 13:27           ` Ivo van Doorn [this message]
2008-03-30 16:32             ` Bas Hulsken
2008-03-30 16:49               ` Mattias Nissler
2008-03-31 12:01       ` Johannes Berg
2008-03-31 12:51         ` Ivo van Doorn
2008-03-31 12:56           ` Johannes Berg

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=200803301527.34583.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=bhulsken@hotmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@baker-net.org.uk \
    /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).