I found this note with similar kernel log like yours:
http://www.linuxforums.org/forum/hardware-peripherals/195227-tl-wn722n-backtrack-5-a.html
Can you please test this workaround?
Am 27.12.2014 um 05:05 schrieb Jeremy Audet:
Sending this again b/c of a delivery error. [9] Sorry for the
Fixed multiple space issues found by checkpatch.pl in
drivers/staging/rtl8723au/core/rtw_ap.c
Signed-off-by: Matthew Emerson emerson...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_ap.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
[Readded Larry to the CC]
On Saturday, December 27, 2014 12:15:58 AM Christopher Chavez wrote:
My bisection led to a branch commit d17ec4d as the bad commit.
Rather than finding out where the bisection went bad, I added
code to check skb-tail, skb-end, and the length to be added.
At the
Alright, here's lunch [for the people in CET].
On Saturday, December 27, 2014 11:10:16 AM Christian Lamparter wrote:
On Saturday, December 27, 2014 12:15:58 AM Christopher Chavez wrote:
My bisection led to a branch commit d17ec4d as the bad commit.
Rather than finding out where the
Use the helper to get rid of the file operations per debugfs file. The
device driver data contains struct ieee80211_hw pointer and the
struct ath9k_softc pointer is assigned to ieee80211_hw::priv so it can
be accessed in the seq_file read operation.
Cc: ath9k-de...@lists.ath9k.org
Signed-off-by:
Hi all,
Since a few weeks I own a laptop with an Intel Wireless 7260 wireless adapter.
I first noticed that my connection started dropping when I transferred
large files over WiFi.
Later on I noticed this problem when the signal strength was low as well.
I seem to be experiencing the bug
This patchset adds TPC capability to ath9k for AR9002 based chips
*[RFC 1/3]: add TX power per-rate tables to cap TX power in TX descriptor path
*[RFC 2/3]: cap per-packet TX power according to TX power per-rate tables
*[RFC 3/3]: enable per-packet TPC on AR9002 based chips by default
This
Add TX power per-rate tables for MIMO/legacy modes for AR9002 based chips
in order to cap the maximum TX power value per-rate in the TX descriptor path.
Add TX power adjustments for HT40 mode, open loop CCK rates and eeprom power
bias for AR9280 and later chips
Signed-off-by: Lorenzo Bianconi
Add TPC capability to TX descriptor path for AR9002 based chips. Scale
per-packet TX power according to eeprom power bias, power adjustments for
HT40 mode and open loop CCK rates. Cap per-packet TX power according to
TX power per-rate tables
Signed-off-by: Lorenzo Bianconi
Enable per-packet TPC on AR9002 based chips by default
Signed-off-by: Lorenzo Bianconi lorenzo.biancon...@gmail.com
---
drivers/net/wireless/ath/ath9k/debug.c | 5 -
drivers/net/wireless/ath/ath9k/hw.c| 3 +--
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git
On Sat, 2014-12-27 at 03:42 -0500, Matthew Emerson wrote:
Fixed multiple space issues found by checkpatch.pl in
drivers/staging/rtl8723au/core/rtw_ap.c
Hello.
Please strive for more than simple robotic like
adherence to checkpatch messages.
A lot of the time, there is a better way.
diff
On 12/06/14 17:57, Jörg Krause wrote:
First, I just subscribed to this mailing list and copied the subject
from the archive. I didn't know better.
Second, many thanks for this new feature to the Broadcom developers!
I've tested this series of patches with the linux-next-20141205 kernel
on a
Hi,
since v3.19-rc1 I have problems with WiFi (Intel Corporation Dual Band
Wireless-AC 7260) on my laptop. Trying to disable all the radio devices
(WiFi and BT) with the function key of my laptop, which should hard
block the rfkills, causes the following message to be repeated over and
over until
On Sat, Dec 27, 2014 at 8:08 PM, Gabriele Mazzotta
gabriele@gmail.com wrote:
Hi,
since v3.19-rc1 I have problems with WiFi (Intel Corporation Dual Band
Wireless-AC 7260) on my laptop. Trying to disable all the radio devices
(WiFi and BT) with the function key of my laptop, which should
Three lines with more than 80 characters per line have been split in several
lines.
Signed-off-by: Oscar Forner Martinez oscar.forner.marti...@gmail.com
---
drivers/bcma/driver_chipcommon.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
Hi,
On Sat, 2014-12-27 at 20:17 +0100, Sedat Dilek wrote:
On Sat, Dec 27, 2014 at 8:08 PM, Gabriele Mazzotta
gabriele@gmail.com wrote:
Hi,
since v3.19-rc1 I have problems with WiFi (Intel Corporation Dual Band
Wireless-AC 7260) on my laptop. Trying to disable all the radio devices
On Fri, 2014-12-26 at 15:35 +0100, Julia Lawall wrote:
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
On Saturday 27 December 2014 19:47:59 Grumbach, Emmanuel wrote:
Hi,
On Sat, 2014-12-27 at 20:17 +0100, Sedat Dilek wrote:
On Sat, Dec 27, 2014 at 8:08 PM, Gabriele Mazzotta
gabriele@gmail.com wrote:
Hi,
since v3.19-rc1 I have problems with WiFi (Intel Corporation Dual Band
These drivers use 9100-byte receive buffers, thus allocating an skb requires
an O(3) memory allocation. Under heavy memory loads and fragmentation, such
a request can fail. Previous versions of the driver have dropped the packet
and reused the old buffer; however, the new version introduced a bug
On 27 December 2014 at 20:24, Oscar Forner Martinez
oscar.forner.marti...@gmail.com wrote:
Three lines with more than 80 characters per line have been split in several
lines.
Thanks for the next version :)
1) You missed version number. Something like
git format-patch --subject-prefix=PATCH V3
Larry Finger larry.fin...@lwfinger.net writes:
These drivers use 9100-byte receive buffers, thus allocating an skb requires
an O(3) memory allocation. Under heavy memory loads and fragmentation, such
a request can fail. Previous versions of the driver have dropped the packet
and reused the
On Sun, Dec 28, 2014 at 12:44 AM, Rafał Miłecki zaj...@gmail.com wrote:
On 27 December 2014 at 20:24, Oscar Forner Martinez
oscar.forner.marti...@gmail.com wrote:
Three lines with more than 80 characters per line have been split in several
lines.
Signed-off-by: Oscar Forner Martinez
On 12/27/2014 11:50 PM, Kalle Valo wrote:
Larry Finger larry.fin...@lwfinger.net writes:
These drivers use 9100-byte receive buffers, thus allocating an skb requires
an O(3) memory allocation. Under heavy memory loads and fragmentation, such
a request can fail. Previous versions of the driver
23 matches
Mail list logo