From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: david Atkins <david@3adesign.co.uk>, Kalle Valo <kvalo@kernel.org>
Cc: "ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: Multiple Qualcomm Hamilton cards on same host - none working
Date: Thu, 29 Feb 2024 08:04:14 -0800 [thread overview]
Message-ID: <3ce6c8f8-e009-433c-9a22-5dfc75388726@quicinc.com> (raw)
In-Reply-To: <LO0P123MB40574FC63D7EF7424ADB5589D65F2@LO0P123MB4057.GBRP123.PROD.OUTLOOK.COM>
On 2/28/2024 11:21 PM, david Atkins wrote:
> Hi,
>
> Update on this, with an Intel CPU the first NIC is found but the second fails so slightly different behaviour, I'll update bug registered with logs
FYI on Linux Kernel mailing lists it is preferred to either have
interleaved or bottom-posted responses.
<https://docs.kernel.org/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions>
>
> I note there was a patch with a comment:
>
> " * support having multiple identical PCI devices (firmware needs to
> have ATH12K_FW_FEATURE_MULTI_QRTR_ID) "
>
> would this address the issue? and is the updated firmware available?
New firmware would be required. Kalle and I are actively working with
the firmware team to get updated firmware posted publicly.
> In discussion with Qualcomm this week I think understood from them that the ath12k driver will not support Wi-Fi 7 in its current form, is this correct?
The current driver has support for some of the WiFi 7 features but the
major addition, multi-link operation, is not currently available.
prev parent reply other threads:[~2024-02-29 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 7:08 Multiple Qualcomm Hamilton cards on same host - none working david Atkins
2024-02-07 11:34 ` Kalle Valo
2024-02-09 10:27 ` david Atkins
2024-02-13 17:54 ` david Atkins
2024-02-29 7:21 ` david Atkins
2024-02-29 16:04 ` Jeff Johnson [this message]
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=3ce6c8f8-e009-433c-9a22-5dfc75388726@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=david@3adesign.co.uk \
--cc=kvalo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox