ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Sustek Goran <goran.sustek@adcubum.com>,
	ath10k <ath10k@lists.infradead.org>,
	Wen Gong <wgong@codeaurora.org>
Subject: Re: [PATCH] ath: add support for special 0x0 regulatory domain
Date: Wed, 23 Dec 2020 13:01:13 +0200	[thread overview]
Message-ID: <87czz06b2e.fsf@codeaurora.org> (raw)
In-Reply-To: <CA+ASDXP8NoGACT4OBEwMvj9B6KsBYBAwMhxSApb7D-fCvfxwTg@mail.gmail.com> (Brian Norris's message of "Tue, 22 Dec 2020 10:30:29 -0800")

Brian Norris <briannorris@chromium.org> writes:

> On Mon, Dec 21, 2020 at 7:43 PM Wen Gong <wgong@codeaurora.org> wrote:
>>
>> On 2020-12-21 05:06, Sustek Goran wrote:
>> > Hi, on my ath10k Chipset,
>> > QCA9984(https://compex.com.sg/shop/wifi-module/802-11ac-wave-2/wle1216v5-20-2/)
>> > afetr this patch i can not longer to initialize my card.
>> >
>> > my dmesg log: So i need to revert this patch! Is my card need
>> > aditional support? Can you please guide what to do for my card to ahve
>> > OOB support in streamline kernels?
>> >
>>
>> If this patch introduce issue to you,
>> I think you can try to revert this patch.
>
> Kalle is still planning on applying my revert patch someday, I think:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20200527165718.129307-1-briannorris@chromium.org/
>
> We just have to wait.

Actually I don't see how I could apply the revert due to the regulatory
problems explained by Jouni[1]. We cannot break regulatory rules.

[1] https://lore.kernel.org/ath10k/CANe27j+fur52HydqqzLc2hBV3QwC2La8+RTJcV=5W5LkUr=PqQ@mail.gmail.com/

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

  reply	other threads:[~2020-12-23 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0BEB3EB4-E3AF-4236-BACC-E42CE2D094B7@adcubum.com>
2020-12-22  3:42 ` [PATCH] ath: add support for special 0x0 regulatory domain Wen Gong
2020-12-22 18:30   ` Brian Norris
2020-12-23 11:01     ` Kalle Valo [this message]
2020-12-23 18:18       ` Brian Norris
2021-01-04 12:10       ` Alvin Šipraga
     [not found] <0101016eb614d832-1f2459b1-1555-4ce7-8f90-5704d201bc10-000000@us-west-2.amazonses.com>
2019-12-02 10:08 ` Kalle Valo
     [not found] ` <20191202100833.0C1B9C433CB@smtp.codeaurora.org>
2019-12-02 10:14   ` wgong
     [not found]   ` <82cf5270f491b1e40640eab23a3b9fb7@codeaurora.org>
2019-12-02 10:24     ` Kalle Valo
2019-11-29  7:34 Wen Gong

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=87czz06b2e.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=briannorris@chromium.org \
    --cc=goran.sustek@adcubum.com \
    --cc=wgong@codeaurora.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 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).