All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mitchell Nordine <mail@mitchellnordine.com>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Ordering Dell XPS 13 9310 to test QCA6390
Date: Wed, 16 Dec 2020 17:46:12 +0200	[thread overview]
Message-ID: <87mtydwy7v.fsf@codeaurora.org> (raw)
In-Reply-To: <tQQZLjnfaM2XZ-LdgoSYE_9yQQmGCtzT108xBh-SzpRhHN7o6_w_jdIcfp67hVNe-kkiNC72u_rhyo1AtUw-41nvcCo_K3pUhkR__6VF6ig=@mitchellnordine.com> (Mitchell Nordine's message of "Wed, 16 Dec 2020 14:41:10 +0000")

Mitchell Nordine <mail@mitchellnordine.com> writes:

>> But I have now ordered Dell XPS 13 laptop and I should get it in
> three weeks, keeping fingers crossed. That should make things easier
> as I can test patches myself.
>
> Hi Kalle, you may already be aware of this, but I just wanted to make sure!
>
> Not all Dell XPS 13 9310 laptops come with the AX500 connectivity chip
> (the one that uses the QCA6390). It seems that only the models with
> 32GB RAM tend to come with the AX500 wifi chip.
>
> Most models appear to come with the AX1650 which I believe uses a
> totally different chip and driver that is already well supported in
> Linux.
>
> It might be worth double-checking the model that you have ordered has the AX500.

I had heard about that so I did order the 32 GB RAM model and multiple
times specified that I only want AX500. So I'm optimistic that I should
get the right chip, but you never know how it goes :) Thanks for
checking, though!

-- 
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

  reply	other threads:[~2020-12-16 15:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 14:41 Ordering Dell XPS 13 9310 to test QCA6390 Mitchell Nordine
2020-12-16 15:46 ` Kalle Valo [this message]
2021-01-13 10:25   ` Kalle Valo
2021-01-13 10:40     ` wi nk
2021-01-13 11:54       ` Kalle Valo
2021-01-13 12:02         ` wi nk
2021-01-13 15:22           ` [**EXTERNAL**] " Luo, Sining
2021-01-13 17:05             ` Kalle Valo
2021-01-13 18:29               ` Luo, Sining
2021-01-16 14:10                 ` Justin Mazzola Paluska
2021-02-12  7:14                   ` Kalle Valo
2021-02-13 19:10                     ` Justin Mazzola Paluska
2021-02-22 16:10           ` Kalle Valo
2021-02-24  9:14             ` Stelian Pop
2021-02-24 21:33               ` Justin Mazzola Paluska
2021-02-24 22:02                 ` Stelian Pop
2021-02-24 22:38                   ` Justin Mazzola Paluska
2021-02-25  8:21                     ` Stelian Pop
2021-03-06 20:22                     ` Wren Turkal
2021-03-06 20:49                       ` Stelian Pop
2021-03-07  4:48                         ` Wren Turkal

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=87mtydwy7v.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mail@mitchellnordine.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 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.