Hi Samuel,
On Tue, May 16, 2017 at 11:42:29AM +0200, Johan Hovold wrote:
> On Thu, Apr 27, 2017 at 12:42:38AM +0200, Samuel Ortiz wrote:
> > Hi Johan,
> >
> > On Thu, Mar 30, 2017 at 12:15:34PM +0200, Johan Hovold wrote:
> > > This started out with the observation that the nfcmrvl_uart driver
>
Hi Jérôme,
On Wed, 2017-05-24 at 07:33 -0400, Jérôme Carretero wrote:
> Hi,
>
>
> I've crippled a Raspberry Pi 3 (1 core, 200 MHz) and observed that the
> glomming feature has a definite impact on TX performance, but it looks
> like at this CPU frequency, the work queue is solicited "too often"
Hans de Goede wrote:
> From: Arend Van Spriel
>
> For SDIO the alignment requirement for transfers from device to host
> is configured in firmware. This configuration is limited to minimum
> of 4-byte alignment. However, this is not correct for platforms using
> 64-bit DMA when the minimum alig
Brian Norris writes:
> In general, it's helpful to use the same code for device removal as for
> device reset, as this tends to have fewer bugs. Let's move the wiphy
> unregistration code into the common reset and removal code.
>
> In particular, it's very hard to properly handle the reset sequen
On 01-06-17 09:44, Hegr, Jiri wrote:
> Dears,
> We use small WiFi evaluation board WM-BN-BM-04_EVB_V1.2 with BCM43362 chip
> (Broadcom).
> This board is connected to OMAP-L138 via SDIO interface with Linux 4.9.10
> containing WiFi driver brcmfmac.
> Our problem is in OOB interrupt. The driver (an
Larry Finger wrote:
> From: Yan-Hsuan Chuang
>
> This patch updates the btcoexist to a newer version with some callbacks.
>
> Specific issues fixed are
> pre_load_firmware()
> fix the unstable issues before FW is ready
> power_on_seting()
> fix the unstable issues before HW is read
Jia-Ju Bai wrote:
> The driver may sleep under a spin lock, and the function call path is:
> cw1200_tx_confirm_cb (acquire the lock by spin_lock)
> __cw1200_cqm_bssloss_sm
> cancel_work_sync --> may sleep
>
> cw1200_cqm_bssloss_sm
> __cw1200_cqm_bssloss_sm
> cancel_work_sync --> may
Colin Ian King wrote:
> From: Colin Ian King
>
> mac is being assigned twice, remove redundant 2nd assignment.
>
> Detected by CoverityScan, CID#1437554 ("Incorrect expression")
>
> Signed-off-by: Colin Ian King
> Acked-by: Sergey Matyukevich
Patch applied to wireless-drivers-next.git, tha
Xinming Hu wrote:
> From: Xinming Hu
>
> AP interface need process remain-on-channel firmware event and notify
> cfg80211, this will be used in the listen-stage of p2p find procedure.
>
> Signed-off-by: Xinming Hu
Patch applied to wireless-drivers-next.git, thanks.
1f7171995142 mwifiex: uap
Shawn Lin wrote:
> We don't need to check if the list is empty separately
> as we could use list_first_entry_or_null to cover it.
>
> Signed-off-by: Shawn Lin
> Reviewed-by: Brian Norris
Patch applied to wireless-drivers-next.git, thanks.
01926202b34b mwifiex: simplify the code around ra_lis
amit karwar wrote:
> linux-firmware maintainers prefer to have a subdirectory for
> firmware files. Code is changed here to pick firmware file from
> a subdirectory. Firmware file with a new loading mechanism will
> be submitted inside rsi directory.
>
> Signed-off-by: Amitkumar Karwar
Patch a
Larry Finger wrote:
> From: Yan-Hsuan Chuang
>
> Delete unused is_wifi_status_changed for 21a 1 ant
>
> Signed-off-by: Yan-Hsuan Chuang
> Signed-off-by: Larry Finger
> Cc: Ping-Ke Shih
> Cc: Birming Chiu
> Cc: Shaofu
> Cc: Steven Ting
Failed to apply without patch 1 so need to drop thes
Ben Greear wrote:
> ath10k firmware checks nbytes == 0 as part of determining if DMA
> has completed successfully. To help make this work more often,
> have the driver initialize nbytes to zero when freeing the descriptor
> slot.
>
> Signed-off-by: Ben Greear
> Signed-off-by: Kalle Valo
Patc
ako...@qti.qualcomm.com wrote:
> QCA99X0, QCA9888, QCA9984 supports calibration data in
> either OTP or DT/pre-cal file. Current ath10k supports
> Calibration data from OTP only.
>
> If caldata is loaded from DT/pre-cal file, fetching board id
> and applying calibration parameters like tx power g
ryan...@qti.qualcomm.com wrote:
> The original idea is to limit the maximum TDLS peer link, but the logic
> is always false, and never be able to restrict the number of TDLS peer
> creation.
>
> Fix the logic here and also move the checking earlier, so that it could
> avoid to handle the failure
Arend van Spriel writes:
> On 31-05-17 14:16, Kalle Valo wrote:
>> Adrian Chadd writes:
>>
>>> This adds a few configurable debugging options:
>>>
>>> * driver debugging and tracing is now configurable per device
>>> * driver debugging and tracing is now configurable at runtime
>>> * the debugg
On 1 June 2017 at 06:24, Kalle Valo wrote:
> Arend van Spriel writes:
>
>> On 31-05-17 14:16, Kalle Valo wrote:
>>> Adrian Chadd writes:
>>>
This adds a few configurable debugging options:
* driver debugging and tracing is now configurable per device
* driver debugging and tr
Adrian Chadd writes:
--- a/drivers/net/wireless/ath/ath10k/core.c
+++ b/drivers/net/wireless/ath/ath10k/core.c
@@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t
priv_size, struct device *dev,
ar->hw_rev = hw_rev;
ar->hif.ops = hif_ops;
On Tue, May 23, 2017 at 10:56 PM, Alexey Brodkin
wrote:
> Hi Amit!
>
> On Tue, 2017-05-23 at 17:00 +0530, amit karwar wrote:
>> On Wed, May 17, 2017 at 1:41 PM, Alexey Brodkin
>> wrote:
>> >
>> > Hello Amitkumar, Prameela,
>> >
>> > I was lucky enough to get hold of RS9113 Evaluation Kit and now
Hi Amit!
On Thu, 2017-06-01 at 19:24 +0530, amit karwar wrote:
> On Tue, May 23, 2017 at 10:56 PM, Alexey Brodkin
> wrote:
>
> I have posted a firmware image for new firmware loading mechanism to
> community. There are some patches for SDIO specific driver
> enhancements and fixes. I am sending
On Thu, 01 Jun 2017 09:05:07 +0800
Jia-Ju Bai wrote:
> I admit my patches are not well tested, and they may not well fix the bugs.
> I am looking forward to opinions and suggestions :)
May I politely suggest that sending out untested locking changes is a
dangerous thing to do? You really should
On Wed, May 31, 2017 at 06:49:43PM +0530, Amitkumar Karwar wrote:
> This image will be loaded by rsi driver. Firmware version is 1.5.3
>
> Signed-off-by: Amitkumar Karwar
Applied, thanks Amitkumar.
--kyle
> ---
> WHENCE | 3 +++
> rsi/rs9113_wlan_qspi.rps | Bin 0 -> 199180
On Thu, Jun 01, 2017 at 12:15:45PM +0300, Kalle Valo wrote:
> Brian Norris writes:
>
> > In general, it's helpful to use the same code for device removal as for
> > device reset, as this tends to have fewer bugs. Let's move the wiphy
> > unregistration code into the common reset and removal code.
On 06/01/2017 11:11 AM, Jonathan Corbet wrote:
On Thu, 01 Jun 2017 09:05:07 +0800
Jia-Ju Bai wrote:
I admit my patches are not well tested, and they may not well fix the bugs.
I am looking forward to opinions and suggestions :)
May I politely suggest that sending out untested locking changes
Begin forwarded message:
Date: Thu, 01 Jun 2017 06:55:22 +
From: bugzilla-dae...@bugzilla.kernel.org
To: step...@networkplumber.org
Subject: [Bug 195953] New: Possible access to unintended variable in
"linux/net/mac80211/sta_info.c" line 2158
https://bugzilla.kernel.org/show_bug.cgi?id=19
Thanks Stephen, I'll take the bug and fix it.
johannes
Report per chain RSSI
Signed-off-by: Norik Dzhandzhapanyan
---
drivers/net/wireless/ath/ath10k/htt_rx.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c
b/drivers/net/wireless/ath/ath10k/htt_rx.c
index 6c0a821fe79d..110953e0bff9 1006
From: Johannes Berg
In the commit enabling per-CPU station statistics, I inadvertedly
copy-pasted some code to update rx_packets and forgot to change it
to update rx_dropped_misc. Fix that.
This addresses https://bugzilla.kernel.org/show_bug.cgi?id=195953.
Fixes: c9c5962b56c1 ("mac80211: enable
On Wed, May 31, 2017 at 09:30:19PM +0200, Arend van Spriel wrote:
> On 31-05-17 18:31, Paul E. McKenney wrote:
> > On Wed, May 31, 2017 at 03:34:57PM +0200, Arnd Bergmann wrote:
> >> On Wed, May 31, 2017 at 3:12 PM, Paul E. McKenney
> >> wrote:
> >>> On Wed, May 31, 2017 at 12:21:10PM +0200, Arnd
Hi Jia-Ju,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.12-rc3 next-20170601]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/b43legacy-Fix
On 06/02/2017 12:11 AM, Jonathan Corbet wrote:
On Thu, 01 Jun 2017 09:05:07 +0800
Jia-Ju Bai wrote:
I admit my patches are not well tested, and they may not well fix the bugs.
I am looking forward to opinions and suggestions :)
May I politely suggest that sending out untested locking changes
Ciao
Benvenuto al nostro negozio
24.88 euro per gli occhiali da sole di Ray Ban, trasporto libero direttamente
alla vostra casa
web: rbewpt .com
放飞心情，释放真情，愿我们的心灵像湖水般的晶莹清澈，友情像山泉一样源远流长！
On Thu, Jun 1, 2017 at 7:49 PM, Alexey Brodkin
wrote:
> Hi Amit!
>
> On Thu, 2017-06-01 at 19:24 +0530, amit karwar wrote:
>> On Tue, May 23, 2017 at 10:56 PM, Alexey Brodkin
>> wrote:
>>
>> I have posted a firmware image for new firmware loading mechanism to
>> community. There are some patches
33 matches
Mail list logo
