From: Kalle Valo <kvalo@codeaurora.org>
To: Thomas Krause <thomaskrause@posteo.de>
Cc: ath11k@lists.infradead.org
Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Mon, 02 Nov 2020 20:34:11 +0200 [thread overview]
Message-ID: <875z6nvc9o.fsf@codeaurora.org> (raw)
In-Reply-To: <1ce6f735-21ff-db7e-c8dc-d567761964aa@posteo.de> (Thomas Krause's message of "Tue, 20 Oct 2020 22:46:00 +0200")
Thomas Krause <thomaskrause@posteo.de> writes:
> Am 19.10.20 um 10:09 schrieb Kalle Valo:
>>> some variants of Dell XPS 13 9310 model have a QCA6390 device
>> Do you happen to know which models exacly have it? I'm trying to find a
>> reasonably priced laptop with QCA6390 from Finland or EU, no luck yet.
>> Apparently there was a certain Dell XPS 15 9500 model but it was almost
>> 4k EUR.
>
> Dell at least sold the XPS 13 9310 with 32 GB RAM in Germany
> (https://www.dell.com/de-de/shop/laptops/neu-xps-13/spd/xps-13-9310-laptop/cn93212)
> with the QCA6390 device. With around 2300 EUR, this offer is still
> expensive but it's less than the 4000. In the delivery notes they
> called the Wi-Fi card "Killer Wi-Fi 6 AX500-DBS (2 x 2)" (part number
> 555-BFPF) but in the current version of the linked listing this is now
> "Killer Wifi 7 AX500". I'm not sure if the "DBS" part has anything to
> say.
Yeah, that's more reasonable price for a laptop. Thanks, this is very
good info. I'll try to find one from Finland.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-02 18:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 11:01 pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 Thomas Krause
2020-10-19 8:09 ` Kalle Valo
2020-10-20 20:46 ` Thomas Krause
2020-11-02 18:34 ` Kalle Valo [this message]
2020-11-02 18:49 ` Kalle Valo
2020-11-02 20:57 ` Bjorn Helgaas
2020-11-03 3:01 ` Carl Huang
2020-11-03 6:49 ` Kalle Valo
2020-11-03 16:08 ` Bjorn Helgaas
2020-11-03 21:08 ` Thomas Gleixner
2020-11-03 22:42 ` Thomas Gleixner
2020-11-09 18:44 ` Kalle Valo
2020-11-04 13:04 ` Thomas Krause
2020-11-04 15:26 ` Thomas Gleixner
2020-11-05 13:23 ` Kalle Valo
2020-11-06 11:57 ` Stefani Seibold
2020-11-10 8:33 ` Kalle Valo
2020-11-11 8:53 ` Thomas Krause
2020-11-11 9:22 ` Kalle Valo
2020-11-11 19:10 ` Kalle Valo
2020-11-11 19:24 ` wi nk
2020-11-11 19:30 ` wi nk
2020-11-11 19:45 ` Kalle Valo
2020-11-11 20:12 ` wi nk
2020-11-11 21:35 ` Stefani Seibold
2020-11-11 22:02 ` Stefani Seibold
2020-11-12 0:24 ` wi nk
2020-11-12 1:10 ` wi nk
2020-11-12 1:11 ` wi nk
2020-11-12 2:31 ` wi nk
2020-11-12 6:29 ` Carl Huang
2020-11-12 7:05 ` Stefani Seibold
2020-11-12 7:15 ` Kalle Valo
2020-11-12 7:41 ` wi nk
2020-11-12 8:59 ` Kalle Valo
2020-11-12 15:44 ` wi nk
2020-11-13 9:52 ` wi nk
2020-11-15 13:30 ` Thomas Krause
2020-11-15 19:55 ` wi nk
2020-11-17 15:49 ` wi nk
2020-11-17 20:59 ` Thomas Gleixner
2020-11-18 10:22 ` wi nk
2020-11-11 9:39 ` Thomas Gleixner
2020-11-06 11:45 ` Devin Bayer
2020-11-09 18:48 ` Kalle Valo
2020-11-03 11:20 ` Devin Bayer
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=875z6nvc9o.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=thomaskrause@posteo.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