From: "Michael Büsch" <mb@bu3sch.de>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Ben Hutchings <ben@decadent.org.uk>,
Stefano Brivio <stefano.brivio@polimi.it>,
linux-wireless@vger.kernel.org, 588196@bugs.debian.org
Subject: Re: Bug#588196: b43: does not join multicast groups
Date: Wed, 14 Jul 2010 14:41:09 +0200 [thread overview]
Message-ID: <4C3DB065.70009@bu3sch.de> (raw)
In-Reply-To: <20100714075037.GA6128@richter> (sfid-20100714_095042_113832_34B70D3D)
On 07/14/2010 09:50 AM, Simon Richter wrote:
> Hi,
>
> On Tue, Jul 13, 2010 at 04:05:10PM +0200, Michael Büsch wrote:
>
>> So it is up to the upper layer to detect the failure. I don't think
>> it's possible to automatically detect such incidents for multicast
>> transmissions. So the mechanism fails here.
>
> Well, it is about *receiving* a multicast transmission
The same applies to receiving. The RX queue is also dropped on switch
from DMA to PIO.
> advertisement, sent to 33:33:00:00:00:01). I have no idea where the
> packet is dropped; from my somewhat limited understanding of 802.11, I'd
> expect the frames to be treated like broadcast frames by the AP, so it'd
> be the receiver dropping them in the MAC filter.
The actual switch from DMA to PIO mode completely reinitializes
the hardware and drops all queues.
--
Greetings Michael.
next prev parent reply other threads:[~2010-07-14 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100706021937.11147.78230.reportbug@debian.hogyros.de>
2010-07-11 22:25 ` Bug#588196: b43: does not join multicast groups Ben Hutchings
2010-07-11 22:57 ` Larry Finger
2010-07-13 5:14 ` Simon Richter
2010-07-13 5:37 ` Larry Finger
2010-07-13 7:37 ` Simon Richter
2010-07-13 13:00 ` Michael Büsch
2010-07-13 13:06 ` Simon Richter
2010-07-13 14:05 ` Michael Büsch
2010-07-14 7:50 ` Simon Richter
2010-07-14 12:41 ` Michael Büsch [this message]
2010-07-15 8:51 ` Simon Richter
2010-07-15 13:45 ` Michael Büsch
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=4C3DB065.70009@bu3sch.de \
--to=mb@bu3sch.de \
--cc=588196@bugs.debian.org \
--cc=Larry.Finger@lwfinger.net \
--cc=Simon.Richter@hogyros.de \
--cc=ben@decadent.org.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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).