All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	voncken <cedric.voncken@acksys.fr>
Subject: Re: ATH10K VLAN firmware issue
Date: Mon, 7 Nov 2016 18:06:03 +0000	[thread overview]
Message-ID: <871syn5fnb.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <CABUTiXW5QSh2KkD+sQ-6QOD5zTce0dun+nyfAMnvL580U=OVNw@mail.gmail.com>	(Bruno Antunes's message of "Mon, 7 Nov 2016 12:01:01 +0000")

Bruno Antunes <baantunes@gmail.com> writes:

> On 4 November 2016 at 21:17, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
>> Bruno Antunes <baantunes@gmail.com> writes:
>>
>>> Old thread but I think the issue is still present.
>>>
>>> I'm running a setup with VLANs with WDS and ath10k cards.
>>>
>>> To make it work both cards must be loaded in rawmode, AP
>>> and Sta, and with no security.
>>>
>>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>>
>>> Although it works the throughput is very bad.
>>> Are there any alternatives to improve the throughput.
>>
>> Can someone file a bug to bugzilla about this so that all the info is
>> properly stored? The more comprehensive the report is the better.
>>
>> https://bugzilla.kernel.org/
>
> I will file a bug report.

Thanks, it's good to store all in one place so that it's easier to find
the relevant info.

> But since it appears to be a firmware related issue
> under what category can fill in the bug?

You can file it under Drivers/network-wireless, AFAIK we don't have any
separate components for firmware bugs. Here's one example to follow:

https://bugzilla.kernel.org/show_bug.cgi?id=186161

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

WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: unlisted-recipients:; (no To-header on input)
Cc: voncken <cedric.voncken@acksys.fr>,
	OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ATH10K VLAN firmware issue
Date: Mon, 7 Nov 2016 18:06:03 +0000	[thread overview]
Message-ID: <871syn5fnb.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <CABUTiXW5QSh2KkD+sQ-6QOD5zTce0dun+nyfAMnvL580U=OVNw@mail.gmail.com>       (Bruno Antunes's message of "Mon, 7 Nov 2016 12:01:01 +0000")

Bruno Antunes <baantunes@gmail.com> writes:

> On 4 November 2016 at 21:17, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
>> Bruno Antunes <baantunes@gmail.com> writes:
>>
>>> Old thread but I think the issue is still present.
>>>
>>> I'm running a setup with VLANs with WDS and ath10k cards.
>>>
>>> To make it work both cards must be loaded in rawmode, AP
>>> and Sta, and with no security.
>>>
>>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>>
>>> Although it works the throughput is very bad.
>>> Are there any alternatives to improve the throughput.
>>
>> Can someone file a bug to bugzilla about this so that all the info is
>> properly stored? The more comprehensive the report is the better.
>>
>> https://bugzilla.kernel.org/
>
> I will file a bug report.

Thanks, it's good to store all in one place so that it's easier to find
the relevant info.

> But since it appears to be a firmware related issue
> under what category can fill in the bug?

You can file it under Drivers/network-wireless, AFAIK we don't have any
separate components for firmware bugs. Here's one example to follow:

https://bugzilla.kernel.org/show_bug.cgi?id=3D186161

--=20
Kalle Valo=

  reply	other threads:[~2016-11-07 18:06 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 14:29 ATH10K VLAN firmware issue Cedric VONCKEN
2015-12-08 14:29 ` Cedric VONCKEN
2015-12-09 15:33 ` Ben Greear
2015-12-09 15:33   ` Ben Greear
2015-12-09 17:24   ` voncken
2015-12-09 17:24     ` voncken
2016-11-04 14:13     ` Bruno Antunes
2016-11-04 14:13       ` Bruno Antunes
     [not found]       ` <27f802e7-79c5-a17f-1883-88e62a6520ef@ezplanet.net>
2016-11-04 14:41         ` [OpenWrt-Devel] " Bruno Antunes
2016-11-04 14:41           ` Bruno Antunes
2016-11-04 17:28           ` yu-chieh kung
2016-11-04 17:28             ` yu-chieh kung
2016-11-04 21:50             ` Ben Greear
2016-11-04 21:50               ` Ben Greear
2016-11-04 22:23               ` Ben Greear
2016-11-04 22:23                 ` Ben Greear
2016-11-05  8:05                 ` Sebastian Gottschall
2016-11-05  8:05                   ` Sebastian Gottschall
2016-11-05 14:35                   ` Ben Greear
2016-11-05 14:35                     ` Ben Greear
2016-11-15 14:37                     ` voncken
2016-11-15 14:37                       ` voncken
2016-11-15 14:55                       ` Ben Greear
2016-11-15 14:55                         ` Ben Greear
2016-11-15 15:00                         ` Bruno Antunes
2016-11-15 15:00                           ` Bruno Antunes
2016-11-15 15:06                           ` Ben Greear
2016-11-15 15:06                             ` Ben Greear
2016-11-07 11:54                 ` Bruno Antunes
2016-11-07 11:54                   ` Bruno Antunes
2016-11-07 14:06                   ` Ben Greear
2016-11-07 14:06                     ` Ben Greear
2016-11-07 14:13                     ` Bruno Antunes
2016-11-07 14:13                       ` Bruno Antunes
2016-11-04 21:17       ` Valo, Kalle
2016-11-04 21:17         ` Valo, Kalle
2016-11-07 12:01         ` Bruno Antunes
2016-11-07 12:01           ` Bruno Antunes
2016-11-07 18:06           ` Valo, Kalle [this message]
2016-11-07 18:06             ` Valo, Kalle
2016-11-07 18:40             ` [OpenWrt-Devel] " Bruno Antunes
2016-11-07 18:40               ` Bruno Antunes
2016-11-15 13:43               ` Valo, Kalle
2016-11-15 13:43                 ` Valo, Kalle
2016-11-15 14:53                 ` Bruno Antunes
2016-11-15 14:53                   ` Bruno Antunes
2017-02-21 12:59                 ` voncken
2017-02-21 12:59                   ` voncken
2017-02-21 13:19                   ` Valo, Kalle
2017-02-21 13:19                     ` Valo, Kalle
     [not found]                     ` <CAKR_QVLpSWab-kF-f8=xqw+oWAfA966GDm7CtXrWfzmJz8gP-w@mail.gmail.com>
2017-02-21 16:47                       ` Bruno Antunes
2017-02-21 16:47                         ` Bruno Antunes
2017-02-22 13:55                     ` voncken
2017-02-22 13:55                       ` voncken

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=871syn5fnb.fsf@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=cedric.voncken@acksys.fr \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    /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.