From: Hauke Mehrtens <hauke@hauke-m.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Michael Büsch" <m@bues.ch>,
b43-dev <b43-dev@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: b43: DMA errors with BCM4331 on BCM4706
Date: Mon, 05 Aug 2013 18:27:50 +0200 [thread overview]
Message-ID: <51FFD286.7040009@hauke-m.de> (raw)
In-Reply-To: <51FD4274.3010108@lwfinger.net>
On 08/03/2013 07:48 PM, Larry Finger wrote:
> On 08/03/2013 11:55 AM, Michael B?sch wrote:
>> 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.
>
> Could it possibly work with short packets, but fail on longer ones?
>
> Larry
Hi,
Thanks for the hints, in fact it was the size and I got my BCM4331 in
the Access Point connected to a BCM4706 working. The problem was that
the the PCIe controller used a PCIe max request size of 128, we try to
change it in driver_pci_host.c, see "MRRS 512", but that does not get
applied to the hardware, when reading it back it is not set, the Max
payload size is changed. The BCM4331 uses a max request size of 512 by
default and that causes problems. I solved the problem by setting the
max request size to 128 for the BCM4331, pcie_set_readrq(bus->host_pci,
128) and then it worked.
The patch is currently just in OpenWrt [0], I will send the patches to
the mailing list in the next days.
@Rafa? If you haven't found a BCM4331, now you can use the one in your
Access Point. ;-)
Hauke
[0]: https://dev.openwrt.org/changeset/37709
WARNING: multiple messages have this Message-ID (diff)
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Michael Büsch" <m@bues.ch>,
b43-dev <b43-dev@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: b43: DMA errors with BCM4331 on BCM4706
Date: Mon, 05 Aug 2013 18:27:50 +0200 [thread overview]
Message-ID: <51FFD286.7040009@hauke-m.de> (raw)
In-Reply-To: <51FD4274.3010108@lwfinger.net>
On 08/03/2013 07:48 PM, Larry Finger wrote:
> On 08/03/2013 11:55 AM, Michael Büsch wrote:
>> 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.
>
> Could it possibly work with short packets, but fail on longer ones?
>
> Larry
Hi,
Thanks for the hints, in fact it was the size and I got my BCM4331 in
the Access Point connected to a BCM4706 working. The problem was that
the the PCIe controller used a PCIe max request size of 128, we try to
change it in driver_pci_host.c, see "MRRS 512", but that does not get
applied to the hardware, when reading it back it is not set, the Max
payload size is changed. The BCM4331 uses a max request size of 512 by
default and that causes problems. I solved the problem by setting the
max request size to 128 for the BCM4331, pcie_set_readrq(bus->host_pci,
128) and then it worked.
The patch is currently just in OpenWrt [0], I will send the patches to
the mailing list in the next days.
@Rafał If you haven't found a BCM4331, now you can use the one in your
Access Point. ;-)
Hauke
[0]: https://dev.openwrt.org/changeset/37709
next prev parent reply other threads:[~2013-08-05 16:27 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
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 [this message]
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=51FFD286.7040009@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--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.