All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>, Jasmine Strong <jas@eero.com>
Cc: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames
Date: Tue, 24 Oct 2017 09:09:18 -0700	[thread overview]
Message-ID: <59EF65AE.8060803@candelatech.com> (raw)
In-Reply-To: <8760b5cfnz.fsf@kamboji.qca.qualcomm.com>

On 10/23/2017 09:50 PM, Kalle Valo wrote:
> Jasmine Strong <jas@eero.com> writes:
>
>> That's what I saw.  A bcom client was able to associate and not pass
>> any traffic.  This is on all three of 9882, 9888 and 4019.
>
> Thanks for the report, we'll investigate it. And I see that your email
> was now succesfully delivered to the list:
>
> http://lists.infradead.org/pipermail/ath10k/2017-October/010325.html


I'm not sure if this is helpful or not, but in the transition from 10.1 to 10.2 firmware,
there was some tricky re-work of the PN counter logic in the firmware source.  It had
specific impact on the broadcom driver interaction.

Possibly a similar issue is being seen with this driver patch?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>, Jasmine Strong <jas@eero.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames
Date: Tue, 24 Oct 2017 09:09:18 -0700	[thread overview]
Message-ID: <59EF65AE.8060803@candelatech.com> (raw)
In-Reply-To: <8760b5cfnz.fsf@kamboji.qca.qualcomm.com>

On 10/23/2017 09:50 PM, Kalle Valo wrote:
> Jasmine Strong <jas@eero.com> writes:
>
>> That's what I saw.  A bcom client was able to associate and not pass
>> any traffic.  This is on all three of 9882, 9888 and 4019.
>
> Thanks for the report, we'll investigate it. And I see that your email
> was now succesfully delivered to the list:
>
> http://lists.infradead.org/pipermail/ath10k/2017-October/010325.html


I'm not sure if this is helpful or not, but in the transition from 10.1 to 10.2 firmware,
there was some tricky re-work of the PN counter logic in the firmware source.  It had
specific impact on the broadcom driver interaction.

Possibly a similar issue is being seen with this driver patch?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-10-24 16:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 16:28 [PATCH] ath10k: rebuild crypto header in RX data frames Kalle Valo
2017-10-20 16:28 ` Kalle Valo
2017-10-20 19:43 ` Sebastian Gottschall
2017-10-20 19:43   ` Sebastian Gottschall
2017-10-20 20:11 ` Sebastian Gottschall
2017-10-20 20:11   ` Sebastian Gottschall
     [not found]   ` <CAGyitvP0wquoo_8_ma3rcj+riJ5Wgfo7+pmbUOx9pQRwFcQHYA@mail.gmail.com>
2017-10-21  4:42     ` Kalle Valo
2017-10-21  4:42       ` Kalle Valo
2017-10-21  7:58       ` Sebastian Gottschall
2017-10-21  7:58         ` Sebastian Gottschall
2017-10-21  4:46     ` Kalle Valo
2017-10-22 10:26       ` Sebastian Gottschall
2017-10-22 10:31       ` Sebastian Gottschall
2017-10-23 18:28         ` Jasmine Strong
2017-10-24  4:50           ` Kalle Valo
2017-10-24  4:50             ` Kalle Valo
2017-10-24 16:09             ` Ben Greear [this message]
2017-10-24 16:09               ` Ben Greear
2017-10-24 19:19               ` Jasmine Strong
2017-10-24 19:19                 ` Jasmine Strong
2017-10-23 14:24   ` Vasanthakumar Thiagarajan
2017-10-23 14:24     ` Vasanthakumar Thiagarajan
2017-10-23 19:35     ` Sebastian Gottschall
2017-10-23 19:35       ` Sebastian Gottschall

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=59EF65AE.8060803@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=jas@eero.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.gottschall@dd-wrt.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.