From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ig0-f177.google.com ([209.85.213.177]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZHBZm-0001PH-Aa for ath10k@lists.infradead.org; Mon, 20 Jul 2015 13:57:50 +0000 Received: by igbpg9 with SMTP id pg9so37846259igb.0 for ; Mon, 20 Jul 2015 06:57:28 -0700 (PDT) Date: Mon, 20 Jul 2015 09:57:16 -0400 From: Bob Copeland Subject: Re: attempting mesh on ath10k Message-ID: <20150720135716.GB9714@localhost> References: <20150706214921.GF23012@localhost> <20150712142532.GA24495@localhost> <20150713014333.GA14152@localhost> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Michal Kazior Cc: "ath10k@lists.infradead.org" On Mon, Jul 13, 2015 at 10:13:59AM +0200, Michal Kazior wrote: > On 13 July 2015 at 03:43, Bob Copeland wrote: > > Actually, it's any group addressed frame. I tried playing with various > > values for htt_data_tx_ext_tid as well as just using the tid on the frame > > (in mesh group addressed frames still have a qos header with tid=0). > > Just a quick question: did you try applying the sw crypto/raw mode > patch[1] and using it for mesh? > > [1]: https://patchwork.kernel.org/patch/6600721/ I gave this a try and still no luck. But I have working and non-working snapshots with only a few months of changes between them so I can bisect it. -- Bob Copeland %% http://bobcopeland.com/ _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k