From: Larry Finger <Larry.Finger@lwfinger.net>
To: Slade Watkins <slade@sladewatkins.com>,
Wireless <linux-wireless@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: rtw89 driver
Date: Thu, 3 Feb 2022 18:57:06 -0600 [thread overview]
Message-ID: <3721475a-a154-7a1a-ad23-b8a77873f951@lwfinger.net> (raw)
In-Reply-To: <CA+pv=HNuxZXTxu2S5vcz=zF81wWxykQe2im6oKgKiaDPujVjiw@mail.gmail.com>
On 2/3/22 18:26, Slade Watkins wrote:
> Hi there,
> Quick question for wireless folks: would backporting the rtw89
> driver[1] (Realtek 8852AE) to kernels older than 5.16.y be possible at
> some point down the road? I ask this as, when testing a stable build
> of 5.15.y a bit ago, I had an issue where the driver wasn't present
> and the system I was testing it on wasn't happy and started kicking
> errors. (It's fairly new, so I did kind of expect that.) I was,
> however, able to solve this by manually building and installing the
> drivers so it wasn't that big of a deal.
>
> [1] https://github.com/lwfinger/rtw89
If for some reason, you do not like my version of the kernel code in the GitHub
repo that you reference, then you could use the Backports Project.
Backporting a driver into one of the stable trees is not a sanctioned activity.
Stable kernels only get fixes for bugs, not new features such as a complete driver.
At least one distro packages rtw89 as kernel modules the same as my GitHub repo.
That distro is openSUSE, which gets its source from that very repo. There may be
others that provide similar packages.
Larry
next prev parent reply other threads:[~2022-02-04 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:26 rtw89 driver Slade Watkins
2022-02-04 0:57 ` Larry Finger [this message]
2022-02-04 1:03 ` Slade Watkins
[not found] <CA+=fEQPeogtO9qr2ZYob27aH-nsnfu=eTJ4g3qqU7bfEiV5diw@mail.gmail.com>
2021-11-10 11:10 ` Fwd: " Nikolay Stanchev
2021-11-11 5:51 ` Pkshih
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=3721475a-a154-7a1a-ad23-b8a77873f951@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=slade@sladewatkins.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;
as well as URLs for NNTP newsgroup(s).