All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Patricio Ferraggi Ares <pattferraggi@gmail.com>
Cc: Mark Herbert <mark.herbert42@gmail.com>,  ath11k@lists.infradead.org
Subject: Re: Fwd: AX500 support quirks
Date: Tue, 15 Feb 2022 14:56:06 +0200	[thread overview]
Message-ID: <87o8381e6x.fsf@kernel.org> (raw)
In-Reply-To: <CAGYwnbk9mUim8GvzLYqqkHLNjtJdQUMqhP1+82s3tCnRHRam=w@mail.gmail.com> (Patricio Ferraggi Ares's message of "Tue, 15 Feb 2022 12:29:31 +0100")

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

> Hey folks,
>
> So. I am still using arch linux, but not everything is working.
> I have decided to give it a try and dive deeper by trying to compile
> my own kernel with the necessary modules and firmware for Wifi and
> Bluetooth.
>
> Could you guys share with me which repos (apart from the kernel
> source) I should use in order to build something based on the latest
> linux-mainline kernel?
> I am unaware of how should I include the latest ath11k drivers from
> Kalle and which modules I need in order to make BT work.
> I would really appreciate it if you could give me some links to the
> repos, some info, and maybe a basic strategy on how to approach this.
> I will search and learn from that starting point.

Arch wiki is a great source for information:

https://wiki.archlinux.org/title/kernel

Arch seems to have a linux-mainline package:

https://aur.archlinux.org/packages/linux-mainline

But questions about compiling the kernel should be sent to distro
support channels as they know best how their distro works, not to ath11k
list.

-- 
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-02-15 12:56 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
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 [this message]
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=87o8381e6x.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mark.herbert42@gmail.com \
    --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.