From: Tom Psyborg <email@example.com> To: Kalle Valo <firstname.lastname@example.org> Cc: "Christian Lamparter" <email@example.com>, "Michał Kazior" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH] ath10k: restore QCA9880-AR1A (v1) detection Date: Tue, 1 Oct 2019 16:17:05 +0200 Message-ID: <CAKR_QVKVFLacWA+qS1=Tyaew-r_J1y--9N2V+eTCOvn3g=5iUg@mail.gmail.com> (raw) In-Reply-To: <email@example.com> Hey Lamperter, I'm sorry if you feel like I hijacked this thread but it was in an obvious attempt to prove more can be done than just returning unsupported message. However, as the company itself is unwilling to provide firmware and everybody mention this chip variant in such a negative context there are obviously some internal reasons to keep it unsupported with silicon bug or two being used as an excuse. Most chips have some hw bugs and workarounds for the same are available, but this didn't result in dropping support for their drivers. So, you can go with this change, but it won't be that useful or required as few others who switch to different card in their router won't need it. For the rest of us 700Mbps with factory TP-Link firmware will suffice.
next prev parent reply index Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-06 21:54 Christian Lamparter 2019-09-07 21:43 ` Sasha Levin 2019-09-07 23:18 ` stable backports for "ath10k: restore QCA9880-AR1A (v1) detection" Christian Lamparter 2019-09-10 1:27 ` [PATCH] ath10k: restore QCA9880-AR1A (v1) detection Tom Psyborg 2019-09-10 7:21 ` Kalle Valo 2019-09-10 12:59 ` Tom Psyborg 2019-09-08 6:32 ` Tom Psyborg 2019-09-17 6:44 ` Kalle Valo 2019-09-18 21:30 ` Tom Psyborg [not found] ` <20190917064412.C2E0D61572@smtp.codeaurora.org> 2019-09-20 17:19 ` Christian Lamparter 2019-10-01 13:03 ` Kalle Valo 2019-10-01 14:17 ` Tom Psyborg [this message] 2019-10-02 17:19 ` Kalle Valo
Reply instructions: You may reply publically 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_QVKVFLacWA+qS1=Tyaew-r_J1y--9N2V+eTCOvn3g=5iUg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Linux-Wireless Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-wireless/0 linux-wireless/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-wireless linux-wireless/ https://lore.kernel.org/linux-wireless \ firstname.lastname@example.org public-inbox-index linux-wireless Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wireless AGPL code for this site: git clone https://public-inbox.org/public-inbox.git