From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Omar Mustafa <omarmustafa1991@yahoo.com>
Cc: Greg KH <greg@kroah.com>, kernelnewbies@kernelnewbies.org
Subject: Re: Vmalloc.h implicit functions
Date: Tue, 07 Sep 2021 18:34:14 -0400 [thread overview]
Message-ID: <48931.1631054054@turing-police> (raw)
In-Reply-To: <B1701F47-C61E-4FF4-9CD4-6F23D386917F@yahoo.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=us-ascii, Size: 1887 bytes --]
On Tue, 07 Sep 2021 18:06:26 +0200, Omar Mustafa said:
> It’s the RTL8822BE Bluetooth which I have tried each and every solution online ever existed and failed
Looks like the PCI card variant has been supported for a while:
[/usr/src/linux-next] git blame drivers/net/wireless/realtek/rtlwifi/pci.c | grep RTL8822BE
e298be2a97fda drivers/net/wireless/realtek/rtlwifi/pci.c (Ping-Ke Shih 2017-12-09 11:37:08 -0600 48) if (rtlhal->hw_type == HARDWARE_TYPE_RTL8822BE) {
89d3e8abcf244 drivers/net/wireless/realtek/rtlwifi/pci.c (Ping-Ke Shih 2017-11-01 10:29:20 -0500 991) if (rtlhal->hw_type == HARDWARE_TYPE_RTL8822BE) {
57869e4ba77a7 drivers/net/wireless/realtek/rtlwifi/pci.c (Ping-Ke Shih 2017-11-01 10:29:19 -0500 1139) else if (rtlhal->hw_type == HARDWARE_TYPE_RTL8822BE)
68929a8380007 drivers/net/wireless/realtek/rtlwifi/pci.c (Ping-Ke Shih 2017-11-01 10:29:21 -0500 1963) rtlhal->hw_type = HARDWARE_TYPE_RTL8822BE;
57869e4ba77a7 drivers/net/wireless/realtek/rtlwifi/pci.c (Ping-Ke Shih 2017-11-01 10:29:19 -0500 1996) case HARDWARE_TYPE_RTL8822BE:
[/usr/src/linux-next] git describe e298be2a97fda
v4.15-rc1-238-ge298be2a97fd
https://linux-hardware.org/index.php?id=usb:0bda-b023 says
the USB flavor is supported by drivers/bluetooth/btusb.c
with config symbols CONFIG_BT CONFIG_BT_HCIBTUSB/
There's an apparently abandoned github driver: https://github.com/lwfinger/rtl8723au_bt
that hasn't been touched in 7 years, and has a Readme that says:
> In this document, we introduce how to support rtk 8723AE/AU BT driver in Linux system.
> Support kernel version 2.6.32~3.13.0
So for us to help you, you're going to have to be a *lot* more detailed about
what kernel release you're using, what the USB/PCI/whatever device you're
working with, and where you got the driver you're trying to get working.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-07 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9C5D07C3-48AA-4E1A-9998-28E94DFCCB08.ref@yahoo.com>
2021-09-07 12:41 ` Vmalloc.h implicit functions Omar Mustafa
2021-09-07 12:53 ` Greg KH
2021-09-07 16:06 ` Omar Mustafa
2021-09-07 16:17 ` Greg KH
2021-09-07 22:34 ` Valdis Klētnieks [this message]
[not found] ` <B4A71321-4D9C-4FB1-BD7D-AB3BF2FE9D7B@yahoo.com>
2021-09-08 5:54 ` Valdis Klētnieks
[not found] ` <6698A2F7-4242-4B6B-9C59-D651FA7337E7@yahoo.com>
2021-09-09 1:39 ` Valdis Klētnieks
[not found] ` <B91EDE80-8B43-415D-9969-AFF2EB3FA414@yahoo.com>
2021-09-15 14:42 ` Greg KH
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=48931.1631054054@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=omarmustafa1991@yahoo.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