Hi Christian,
> On Thursday, December 15, 2016 10:13:39 PM CET Mohammed Shafi Shajakhan wrote:
> > I am also thinking, as of now there is not much use in appending
> > the extended peer stats (which gets periodically ) to the linked list
> > '>debug.fw_stats.peers_extd)' and should we get rid of
On Thu, Dec 15, 2016 at 06:53:47PM +0100, Jean-Pierre Tosoni wrote:
> > > Thanks for the suggestion, I already tried something like this in
> > > wmi.c, with the same result:
> > >
> > > - Before patching the firmware scans DFS channels actively (with
> > probes).
> > >
> > > - After patching, the
> -Message d'origine-
> De : Ben Greear [mailto:gree...@candelatech.com]
> Envoyé : jeudi 15 décembre 2016 17:33
> À : Jean-Pierre Tosoni; 'Jouni Malinen'
> Cc : linux-wirel...@vger.kernel.org; ath10k@lists.infradead.org
> Objet : Re: ath10k firmware sends probes on DFS channels without
On 12/15/2016 05:40 PM, Valo, Kalle wrote:
> Erik Stromdahl writes:
>
>> Initial HIF sdio/mailbox implementation.
>>
>> Signed-off-by: Erik Stromdahl
>> ---
>> drivers/net/wireless/ath/ath10k/Kconfig |6 +
>>
Hello Shafi,
On Thursday, December 15, 2016 10:13:39 PM CET Mohammed Shafi Shajakhan wrote:
> I am also thinking, as of now there is not much use in appending
> the extended peer stats (which gets periodically ) to the linked list
> '>debug.fw_stats.peers_extd)' and should we get rid of the
Hi Christian,
I am also thinking, as of now there is not much use in appending
the extended peer stats (which gets periodically ) to the linked list
'>debug.fw_stats.peers_extd)' and should we get rid of the below
(and the required cleanup as well)
list_splice_tail_init(_extd,
On 12/15/2016 07:22 AM, Jean-Pierre Tosoni wrote:
Jouni,
Thanks for the suggestion, I already tried something like this in wmi.c,
with the same result:
- Before patching the firmware scans DFS channels actively (with probes).
- After patching, the firmware scans DFS channels passively *until*
Jouni,
Thanks for the suggestion, I already tried something like this in wmi.c,
with the same result:
- Before patching the firmware scans DFS channels actively (with probes).
- After patching, the firmware scans DFS channels passively *until* any
beacon is received on the DFS channel. When