From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev <b43-dev@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: b43: DMA errors with BCM4331 on BCM4706
Date: Sat, 3 Aug 2013 18:55:04 +0200 [thread overview]
Message-ID: <20130803185504.022b19d2@milhouse> (raw)
In-Reply-To: <51FD218E.9040700@hauke-m.de>
On Sat, 03 Aug 2013 17:28:14 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> I used wireshark to see what actually happens and the device send out
> beacons and answers to probe requests without problems. I see the
> Authentication, Association Request and Association Response frames and
That suggests DMA works for some packets and then fails?
> Does anybody have any thought on this topic?
You should print out more of the DMA values.
--
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20130803/8827004d/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev <b43-dev@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: b43: DMA errors with BCM4331 on BCM4706
Date: Sat, 3 Aug 2013 18:55:04 +0200 [thread overview]
Message-ID: <20130803185504.022b19d2@milhouse> (raw)
In-Reply-To: <51FD218E.9040700@hauke-m.de>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Sat, 03 Aug 2013 17:28:14 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> I used wireshark to see what actually happens and the device send out
> beacons and answers to probe requests without problems. I see the
> Authentication, Association Request and Association Response frames and
That suggests DMA works for some packets and then fails?
> Does anybody have any thought on this topic?
You should print out more of the DMA values.
--
Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-03 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 15:28 b43: DMA errors with BCM4331 on BCM4706 Hauke Mehrtens
2013-08-03 15:28 ` Hauke Mehrtens
2013-08-03 16:55 ` Michael Büsch [this message]
2013-08-03 16:55 ` Michael Büsch
2013-08-03 17:48 ` Larry Finger
2013-08-03 17:48 ` Larry Finger
2013-08-05 16:27 ` Hauke Mehrtens
2013-08-05 16:27 ` Hauke Mehrtens
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=20130803185504.022b19d2@milhouse \
--to=m@bues.ch \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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 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.