ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: Jeff Johnson <quic_jjohnson@quicinc.com>, ath11k@lists.infradead.org
Subject: Re: State of multiple PCI(e) modules since 2022
Date: Tue, 5 Nov 2024 07:52:08 +0100	[thread overview]
Message-ID: <cc6d59b4-27ec-4362-b7be-8cc1632cad50@ionic.de> (raw)
In-Reply-To: <ceaab3b3-6537-4ea4-bc66-1ee8c48da16a@quicinc.com>


[-- Attachment #1.1: Type: text/plain, Size: 1075 bytes --]

* On 10/31/24 15:49, Jeff Johnson wrote:
> Kalle & I sympathize with you. I've escalated this to my management.

Thank you, that's seriously much appreciated.

But also, I'm not just here to complain.


Based on Denis's work, and on the ath-202411041543 tag, I've modified ath11k and 
ath12k to make use of the new endpoint ID binding feature and finally got an 
ath11k and ath12k card working at the same time (I'm too lazy to put two 
ath11k-based cards into the machine to test whether this also works for now):


5: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN 
mode DORMANT group default qlen 1000
     link/ether 66:a3:69:e9:71:49 brd ff:ff:ff:ff:ff:ff permaddr 20:57:9e:2d:04:1e
6: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
     link/ether 78:46:5c:3b:ab:a7 brd ff:ff:ff:ff:ff:ff


However, I'm not at all happy with the solution and don't even consider it an 
RFC due to the way it integrates. I'll still share the patch set for reference.



Mihai

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-11-05  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-27 14:11 State of multiple PCI(e) modules since 2022 Mihai Moldovan
2024-10-29 16:39 ` Denis Kenzior
2024-10-31 14:49 ` Jeff Johnson
2024-11-05  6:52   ` Mihai Moldovan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 17:05 Mihai Moldovan
2024-11-01 17:17 Mihai Moldovan

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=cc6d59b4-27ec-4362-b7be-8cc1632cad50@ionic.de \
    --to=ionic@ionic.de \
    --cc=ath11k@lists.infradead.org \
    --cc=quic_jjohnson@quicinc.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
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