All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Patricio Ferraggi Ares <pattferraggi@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: Fwd: AX500 support quirks
Date: Thu, 27 Jan 2022 14:29:55 +0200	[thread overview]
Message-ID: <87ilu5jr98.fsf@kernel.org> (raw)
In-Reply-To: <CAGYwnbnBjaNmS7aaSTXKtAbF1tKqeXTT_6tjka=5AS97c7Br8Q@mail.gmail.com> (Patricio Ferraggi Ares's message of "Wed, 26 Jan 2022 12:02:58 +0100")

Patricio Ferraggi Ares <pattferraggi@gmail.com> writes:

> My name is Patricio, I am a fellow software developer and user of the
> Dell XPS 9310 (AX500 version). First of all, I wanted to thank you for
> all your hard work bringing support for this model, thanks to you, I
> have been able to use my laptop with Linux almost since I got it.
>
> This is not a bug report in any way, I just would like to gain some
> knowledge on the subject and you might be the perfect person for my
> questions.
>
> I noticed that although all distros use the Linux kernel, support for
> this hardware is not the same across all Linux distros. To be more
> specific, Ubuntu-based distros have had working wifi and Bluetooth for
> almost a year now, although there are some problems like resuming from
> deep sleep,  both wifi and Bluetooth work right away on installation,
> at the moment I am using Pop OS with Linux kernel 5.15.5 as my main
> driver. On the other hand, arch-based distros dont' have working BT,
> as you can see here and here. The wifi is working but Bluetooth
> sometimes doesn't turn on and when it does it cannot properly connect
> to devices. This happens across multiple arch-based distros and kernel
> versions, even if I try kernel versions that work fine in PopOS, they
> don't in Arch.
>
> So finally, my questions:
>
> Why is there this inconsistency of support between distros when
> theoretically, they are all Linux?
> Why is it that if Arch is always updated, in this particular case
> their hardware support is lacking compared to ubuntu?

This is something you need to ask Ubuntu, or check from their git
history or package changelogs. But in general distros make changes to
the kernel, some of them even quite drastic, so behaviour between
distros can be different. My guess is that Ubuntu had custom changes to
ath11k, maybe they backported patches?

> And finally, do you have a working configuration with wifi and
> Bluetooth? if that is the case could you tell me your distro, kernel,
> firmware, system firmware versions?

I also use Dell XPS 13 9310 with QCA6390 as my daily driver (no pun
intended) and I have no issues with wifi. BIOS is 3.1.0 from 07/22/2021.
I'm a debian guy so I have Debian 10 and use connman, but
network-manager should work as well. I compile my own kernel from my
ath.git master branch[1], but with QCA6390 I would expect stock v5.16
release to work fine. For WCN6855 I recommend to use v5.17.

Firmware version is WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1.

I don't use Bluetooth so can't comment on that.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/

-- 
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:[~2022-01-27 12:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGYwnb=p38NMpWY=wLiPRE7eUDfjE_SyNS9zQ9W7Nhpy6hn+WQ@mail.gmail.com>
2022-01-26 11:02 ` Fwd: AX500 support quirks Patricio Ferraggi Ares
2022-01-27 12:29   ` Kalle Valo [this message]
2022-01-27 13:28     ` Mark Herbert
2022-01-27 13:40       ` Kalle Valo
2022-01-27 13:58       ` Patricio Ferraggi Ares
2022-01-27 18:33         ` Mark Herbert
2022-01-31  9:30           ` Patricio Ferraggi Ares
2022-01-31  9:57             ` Mark Herbert
2022-01-31 11:06             ` Kalle Valo
2022-02-15 11:22               ` Patricio Ferraggi Ares
2022-02-15 11:29               ` Patricio Ferraggi Ares
2022-02-15 12:56                 ` Kalle Valo
2022-02-15 13:03                   ` Patricio Ferraggi Ares
2022-02-15 18:42                     ` Mark Herbert
2022-02-16  6:58                       ` 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=87ilu5jr98.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=pattferraggi@gmail.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.