All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
	Christian Lamparter <chunkeey@gmail.com>
Subject: Re: [PATCH] ath10k: restore QCA9880-AR1A (v1) detection
Date: Tue, 10 Sep 2019 10:21:48 +0300	[thread overview]
Message-ID: <87h85kfwfn.fsf@codeaurora.org> (raw)
In-Reply-To: <CAKR_QVKv8kgXSSCwd8esw28hARA61Pah3usRi+ZZG6ss2CcS=g@mail.gmail.com> (Tom Psyborg's message of "Tue, 10 Sep 2019 03:27:28 +0200")

(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? For example, you could
try the old ath10k and old hw1.0 firmware to see if it works.

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

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

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Tom Psyborg <pozega.tomislav@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
	Christian Lamparter <chunkeey@gmail.com>
Subject: Re: [PATCH] ath10k: restore QCA9880-AR1A (v1) detection
Date: Tue, 10 Sep 2019 10:21:48 +0300	[thread overview]
Message-ID: <87h85kfwfn.fsf@codeaurora.org> (raw)
In-Reply-To: <CAKR_QVKv8kgXSSCwd8esw28hARA61Pah3usRi+ZZG6ss2CcS=g@mail.gmail.com> (Tom Psyborg's message of "Tue, 10 Sep 2019 03:27:28 +0200")

(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? For example, you could
try the old ath10k and old hw1.0 firmware to see if it works.

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

  reply	other threads:[~2019-09-10  7:21 UTC|newest]

Thread overview: 29+ 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-06 21:54 ` Christian Lamparter
2019-09-07 21:43 ` Sasha Levin
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-07 23:18     ` Christian Lamparter
2019-09-10  1:27   ` [PATCH] ath10k: restore QCA9880-AR1A (v1) detection Tom Psyborg
2019-09-10  1:27     ` Tom Psyborg
2019-09-10  7:21     ` Kalle Valo [this message]
2019-09-10  7:21       ` Kalle Valo
2019-09-10 12:59       ` Tom Psyborg
2019-09-10 12:59         ` Tom Psyborg
2019-09-10 13:51         ` Sebastian Gottschall
2019-09-10 14:11           ` Ben Greear
2019-09-10 14:20             ` Sebastian Gottschall
2019-09-08  6:32 ` Tom Psyborg
2019-09-08  6:32   ` Tom Psyborg
2019-09-17  6:44 ` Kalle Valo
2019-09-17  6:44 ` Kalle Valo
2019-09-18 21:30   ` Tom Psyborg
2019-09-18 21:30     ` Tom Psyborg
     [not found] ` <20190917064412.C2E0D61572@smtp.codeaurora.org>
2019-09-20 17:19   ` Christian Lamparter
2019-09-20 17:19     ` Christian Lamparter
2019-10-01 13:03     ` Kalle Valo
2019-10-01 13:03       ` Kalle Valo
2019-10-01 14:17       ` Tom Psyborg
2019-10-01 14:17         ` Tom Psyborg
2019-10-02 17:19 ` Kalle Valo
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=87h85kfwfn.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pozega.tomislav@gmail.com \
    --cc=sashal@kernel.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.