ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@newmedia-net.de>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: restore QCA9880-AR1A (v1) detection
Date: Tue, 10 Sep 2019 07:11:32 -0700	[thread overview]
Message-ID: <a599bf9a-44ad-2d70-79dc-324e8dbeb1cd@candelatech.com> (raw)
In-Reply-To: <a1cf238e-ee80-ee81-f7a6-28faff3a35a6@newmedia-net.de>



On 09/10/2019 06:51 AM, Sebastian Gottschall wrote:
> the tplink archer c7 v1 indeed has this hw 1 version. but thats the only device i know comming with this chipset version
> but the v1 has also a minipcie slot and is not soldered like all other revisions.  so i just replaced the card on my test device.
> in addition we may ask ben grear if he is able to provide a v1 firmware from his ct tree since the qca sourcecodes do contain support
> for the v1 revision. but dont expect too much. there was a reason why v1 was never really on the market

Hello,

I don't think I can even build a v1 firmware if I wanted to, and I'd much rather work on newer
chips.  That v1 was an unstable wreck from the beginning, at least with open-source driver.

Thanks,
Ben

>
> Am 10.09.2019 um 14:59 schrieb Tom Psyborg:
>> On 10/09/2019, Kalle Valo <kvalo@codeaurora.org> wrote:
>>> (dropping stable list)
>>>
>>> Tom Psyborg <pozega.tomislav@gmail.com> writes:
>>>
>>>> According to this very old post
>>>> http://lists.infradead.org/pipermail/ath10k/2013-July/000021.html
>>>> seems like you've been misinformed on amount of these cards that were
>>>> put out in the market.
>>>>
>>>> At least digipart only have >40000 units in stocks
>>>> https://www.digipart.com/part/QCA9880-AR1A and other retailers
>>>> probably few thousands more.
>>>>
>>>> With that large amount of cards I think it is justified to request
>>>> firmware support for the chip. And probably a lot easier to make few
>>>> firmware modifications than go hacking a bunch of API calls so it
>>>> works with v2 firmware.
>>> I'm very surprised that QCA9880 hw1.0 boards are still available, after
>>> six years. Did you confirm that it really is hw1.0 and not just some
>>> mixup with hardware ids or something like that?
>> Print on the chip clearly says QCA9880-AR1A. ID same as for v2 - 003C.
>>
>>> old hw1.0 firmware to see if it works.
>> I don't know which fw blob version that is. I could not find it
>> online. All files are v2 related.
>>
>>> But if it's really is hw1.0 I doubt there will be any support for that.
>>> I recommend to avoid hw1.0 altogether.
>>>
>>> --
>>> Kalle Valo
>>>
>> That would be too bad, even worse when you find out that
>> qca-wifi-10.2.4.58.1 driver fails to load firmware too. The only one
>> that works is qca-wifi that comes with tp-link firmware, some very
>> early version 10.0.108 or somtehing like that that has no available
>> sources..
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

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

  reply	other threads:[~2019-09-10 14:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 21:54 [PATCH] ath10k: restore QCA9880-AR1A (v1) detection 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-10 13:51         ` Sebastian Gottschall
2019-09-10 14:11           ` Ben Greear [this message]
2019-09-10 14:20             ` Sebastian Gottschall
2019-09-08  6:32 ` Tom Psyborg
2019-09-17  6:44 ` Kalle Valo
     [not found] ` <20190917064412.E237C61577@smtp.codeaurora.org>
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
2019-10-02 17:19 ` Kalle Valo

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=a599bf9a-44ad-2d70-79dc-324e8dbeb1cd@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=s.gottschall@newmedia-net.de \
    /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