From: Larry Finger <Larry.Finger@lwfinger.net>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: "Arend van Spriel" <arend@broadcom.com>,
"Julian Calaby" <julian.calaby@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: very bad work of wl (bcm 43228)
Date: Sun, 05 May 2013 17:05:33 -0500 [thread overview]
Message-ID: <5186D7AD.1070702@lwfinger.net> (raw)
In-Reply-To: <CACaajQuk359fYap=547qQ0r128bdCuzFCzR=iXgHNaaR_eTtow@mail.gmail.com>
On 05/05/2013 03:30 PM, Vasiliy Tolstov wrote:
> 2013/4/27 Vasiliy Tolstov <v.tolstov@selfip.ru>:
>> 2013/4/26 Arend van Spriel <arend@broadcom.com>:
>>> Not really. You could try disabling powersave. I am not very familiar with
>>> wl driver.
>>>
>>> $ iw dev wlanX power_save off
>>>
>>> Can you still provide lsusb and lspci for all devices?
>>>
>>> Gr. AvS
>
>
> Any news?
You are using a closed-source driver. None of us know what is in the code, thus
there is very little help we can give you other than to give general
suggestions. If you were using b43 or brcmsmac, the situation would be different.
Larry
next prev parent reply other threads:[~2013-05-05 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 8:27 very bad work of wl (bcm 43228) Vasiliy Tolstov
2013-04-19 10:41 ` Julian Calaby
2013-04-19 10:44 ` Vasiliy Tolstov
2013-04-19 11:06 ` Julian Calaby
2013-04-19 11:20 ` Vasiliy Tolstov
2013-04-19 12:51 ` Julian Calaby
2013-04-19 19:24 ` Arend van Spriel
2013-04-21 12:54 ` Vasiliy Tolstov
2013-04-26 7:17 ` Vasiliy Tolstov
2013-04-26 9:01 ` Arend van Spriel
2013-04-26 20:19 ` Vasiliy Tolstov
2013-05-05 20:30 ` Vasiliy Tolstov
2013-05-05 22:05 ` Larry Finger [this message]
2013-05-06 10:45 ` Vasiliy Tolstov
2013-05-06 15:31 ` Larry Finger
2013-05-07 8:11 ` Arend van Spriel
2013-05-07 14:32 ` Vasiliy Tolstov
2013-05-17 13:30 ` Vasiliy Tolstov
2013-05-17 14:18 ` Arend van Spriel
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=5186D7AD.1070702@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=v.tolstov@selfip.ru \
--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 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).