From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
David Miller <davem@davemloft.net>,
David.Laight@aculab.com, linville@tuxdriver.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
bittorf@bluebottle.com, stable@vger.kernel.org
Subject: Re: [PATCH] b43: Increase number of RX DMA slots
Date: Wed, 20 Feb 2013 01:15:57 -0600 [thread overview]
Message-ID: <5124782D.3050803@lwfinger.net> (raw)
In-Reply-To: <CA+XFjipJHGTvzUx6yy1DTc74kbrPEQxM08zW=N1uf43=Q6pwdg@mail.gmail.com>
On 02/20/2013 12:26 AM, Gábor Stefanik wrote:
>
> Is this an issue that vendor drivers are also vulnerable to? If it is
> a firmware issue, I would certainly think so.
I also think so, at least if they are using the firmware version that Bastian is
using. His logs don't have that info in them, but I certainly saw the problem on
my BCM4312 using firmware 508.154 from 2009.
Larry
next prev parent reply other threads:[~2013-02-20 7:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 3:01 [PATCH] b43: Increase number of RX DMA slots Larry Finger
2013-02-18 3:01 ` Larry Finger
2013-02-18 16:18 ` Rafał Miłecki
2013-02-18 16:18 ` Rafał Miłecki
2013-02-18 16:55 ` Bastian Bittorf
2013-02-18 16:55 ` Bastian Bittorf
2013-02-18 17:04 ` Larry Finger
2013-02-18 20:10 ` Larry Finger
2013-02-19 20:01 ` Bastian Bittorf
2013-02-19 20:01 ` Bastian Bittorf
2013-02-19 5:52 ` David Miller
2013-02-19 5:52 ` David Miller
2013-02-19 9:42 ` David Laight
2013-02-19 9:57 ` Rafał Miłecki
2013-02-19 17:57 ` Larry Finger
2013-02-19 18:15 ` David Miller
2013-02-19 18:28 ` Larry Finger
2013-02-20 0:47 ` Julian Calaby
2013-02-20 2:42 ` Larry Finger
2013-02-20 6:26 ` Gábor Stefanik
2013-02-20 6:26 ` Gábor Stefanik
2013-02-20 7:15 ` Larry Finger [this message]
2013-02-20 8:15 ` Bastian Bittorf
2013-02-20 8:15 ` Bastian Bittorf
2013-02-20 15:49 ` Larry Finger
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=5124782D.3050803@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=David.Laight@aculab.com \
--cc=bittorf@bluebottle.com \
--cc=davem@davemloft.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=stable@vger.kernel.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 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.