From: "Arend van Spriel" <arend@broadcom.com>
To: "Vasiliy Tolstov" <v.tolstov@selfip.ru>
Cc: "Julian Calaby" <julian.calaby@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com,
"Rafał Miłecki" <zajec5@gmail.com>,
"Larry Finger" <larry.finger@lwfinger.net>
Subject: Re: very bad work of wl (bcm 43228)
Date: Fri, 26 Apr 2013 11:01:50 +0200 [thread overview]
Message-ID: <517A427E.3010809@broadcom.com> (raw)
In-Reply-To: <CACaajQtbR5Utac82Zik00dQZYiE=tcDRmhWDt17BYEHDOj1Z2w@mail.gmail.com>
On 04/26/2013 09:17 AM, Vasiliy Tolstov wrote:
> Any news ?
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
> 2013/4/21 Vasiliy Tolstov <v.tolstov@selfip.ru>:
>> 2013/4/19 Arend van Spriel <arend@broadcom.com>:
>>> I have no quick solution so need to more detailed info. For these kind of
>>> questions it always helps to provide kernel log and output from commands
>>> like lspci and lsusb.
>>
>>
>> Now i'm sometimes not able ping my wifi hot spot (only on 43228, on
>> 4311 all works fine with b43 driver)
>> lspci:
>> 03:00.0 0280: 14e4:4359
>> Subsystem: 105b:e04b
>> Flags: bus master, fast devsel, latency 0, IRQ 17
>> Memory at c0500000 (64-bit, non-prefetchable) [size=16K]
>> Capabilities: [40] Power Management version 3
>> Capabilities: [58] Vendor Specific Information: Len=78 <?>
>> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
>> Capabilities: [d0] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [13c] Virtual Channel
>> Capabilities: [160] Device Serial Number 00-00-b9-ff-ff-fc-08-ed
>> Capabilities: [16c] Power Budgeting <?>
>> Kernel driver in use: wl
>> Kernel modules: wl
>>
>>
>> Some logs from kernel and ping in attached file. I'm try to send this
>> email ten times, becouse wifi very bad work's with this driver =(
>>
>> --
>> Vasiliy Tolstov,
>> e-mail: v.tolstov@selfip.ru
>> jabber: vase@selfip.ru
>
>
>
next prev parent reply other threads:[~2013-04-26 9:02 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 [this message]
2013-04-26 20:19 ` Vasiliy Tolstov
2013-05-05 20:30 ` Vasiliy Tolstov
2013-05-05 22:05 ` Larry Finger
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=517A427E.3010809@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=julian.calaby@gmail.com \
--cc=larry.finger@lwfinger.net \
--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 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.