linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Psyborg <pozega.tomislav@gmail.com>
To: John Crispin <john@phrozen.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RESEND] ath10k: add tx hw 802.11 encapusaltion offloading support
Date: Sat, 28 Dec 2019 04:21:10 +0100	[thread overview]
Message-ID: <CAKR_QVJE6c-VTR-rGdBUt08ijt=w2rCRjeNQ2+=E6ZQ6_N+g=Q@mail.gmail.com> (raw)
In-Reply-To: <d2e4207c-1cd6-198e-84df-21496f0be378@phrozen.org>

On 19/12/2019, John Crispin <john@phrozen.org> wrote:
> On 18/12/2019 23:45, Tom Psyborg wrote:
>> ccing Johannes Berg since upstream change (mac80211-next) breaks build:
>>
>> In the commit log its written: remove SUPPORTS_80211_ENCAP HW flag
>>
>> Any sane reasons for doing that? mac80211 fails to build because of
>> removed flags, this is on backports-5.3-rc4
>>
>> Other than that the feature delivers the promised:
>> QCA9880 iperf between wired and wireless machine
>> native mode 449Mbps
>> ethernet mode 522Mbps
>>
>
> superseded due to johill's fixup of the patch, new version coming up
> 	John
>

in case it doesn't fix up scan crash i can provide more details.

triggering scan (from luci at least) would always crash the driver
unless vdev was already started, right after the message: mac create
vdev 0 map ffff

  reply	other threads:[~2019-12-28  3:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  9:22 [RESEND] ath10k: add tx hw 802.11 encapusaltion offloading support John Crispin
2019-12-17 15:30 ` Kalle Valo
2019-12-18 20:14   ` Tom Psyborg
2019-12-18 22:45     ` Tom Psyborg
2019-12-18 23:18       ` John Crispin
2019-12-28  3:21         ` Tom Psyborg [this message]
2019-12-19  6:36       ` Sebastian Gottschall
2019-12-19 10:31         ` Tom Psyborg
2019-12-19 10:44           ` Sebastian Gottschall
2019-12-19 14:39             ` Tom Psyborg
2020-02-13 16:18     ` Kalle Valo
2019-12-28  4:45 ` Justin Capella

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='CAKR_QVJE6c-VTR-rGdBUt08ijt=w2rCRjeNQ2+=E6ZQ6_N+g=Q@mail.gmail.com' \
    --to=pozega.tomislav@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=john@phrozen.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vthiagar@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).