public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: BCM5354
Date: Tue, 08 Jun 2010 07:00:53 +0200	[thread overview]
Message-ID: <4C0DCE85.5000506@bu3sch.de> (raw)
In-Reply-To: <AANLkTimdhwo-KhM3c1mJmyZih4CKPNRKQmVLGNgY8DOg@mail.gmail.com> (sfid-20100607_193840_198990_32ECDE26)

On 06/08/2010 01:38 AM, Chris Martin wrote:
> I to am working on project using openWrt and  the  BCM5354, and we too
> are using the 2.4 kernel.
> However I have been testing the 2.6 with wireless compat (b43)
>
> I was about to log an trac issues with openWrt today, but I
> saw this post so I thought that would add my bit here as well.
>
> I can confirm that It works flawlessly in client mode.  However It fails
> in AP mode.
>
> There are 2 types of errors that I encounter.  NOTE: these problems do
> not appear in STA mode.  I have been using STA mode for over a month -
> all day.   I am currently working on another issue, but once I have that
> solved I was going to start on this.  But in the mean time I DO have
> the resources and the time to test anything that anyone may suggest.
>   and if I find a solution I will obviously be posting it back here.
>
> In AP mode the time it takes for the following errors to occur varies -
> sometimes it will run for 1/2 day OK.  others it
> fails almost immediately - but mostly it is unusable
>
> --------------ERROR 1----------------
>
> b43-phy0 ERROR: DMA RX buffer too small (len: 64653, buffer: 2352,
> nr-dropped: 28)

Hm, the length looks like a negative number (-884). I don't see why the 
firmware should report negative length, however. May also be a simple 
integer underflow for whatever reason.
In any case, I think the firmware probably died and responds with crap. 
Which would also explain the suspend failures.

> b43-phy0 ERROR: MAC suspend failed
> b43-phy0 ERROR: MAC suspend failed

Are there any LP specific hostflags that need to be set in AP mode?

-- 
Greetings Michael.

      parent reply	other threads:[~2010-06-08  5:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 18:33 BCM5354 Robert Hazbun
2010-06-07 18:48 ` BCM5354 Larry Finger
2010-06-07 19:00   ` BCM5354 Michael Büsch
     [not found]   ` <4C0D40C2.7050409@sephix.com>
2010-06-07 19:42     ` BCM5354 Larry Finger
2010-06-07 19:55       ` BCM5354 Robert Hazbun
2010-06-07 20:11         ` BCM5354 Gábor Stefanik
2010-06-07 23:38           ` BCM5354 Chris Martin
2010-06-08  1:14             ` BCM5354 Gábor Stefanik
2010-06-08  2:52               ` BCM5354 Chris Martin
2010-06-08  3:29                 ` BCM5354 Gábor Stefanik
2010-06-08  4:41                   ` BCM5354 Chris Martin
2010-06-08  5:00             ` Michael Büsch [this message]

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=4C0DCE85.5000506@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=b43-dev@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox