Vmalloc.h implicit functions
omarmustafa1991 at yahoo.com
Wed Sep 15 10:32:45 EDT 2021
Sorry for being late but it took me so long to find this:
Is this the driver you were talking about??
> On 9 Sep 2021, at 3:40 AM, Valdis Klētnieks <valdis.kletnieks at vt.edu> wrote:
> On Wed, 08 Sep 2021 12:02:39 +0200, Omar Mustafa said:
>> The driver is RTL8822BE Bluetooth
> That's not what I asked for. And that's not the *driver*, that's
> the *device*.
> For example, this laptop has an Ethernet and a wireless card:
> [~] lspci -nn |grep -i net
> 01:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 07)
> 02:00.0 Network controller : Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
> and there's no RTL810xE or QCA8565 driver. The first actually uses the r8169
> driver, and the second uses the ath9k driver. Both those drivers support a
> wide range of devices. iwlwifi is another driver that supports a whole bunch
> of devices.
> Meanwhile, a USB trackball I use is:
> [~] lsusb | grep Track
> Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
> And those [10ec:8136], [168c:0036], and [045e:0023] are actually important, as
> that is what the *HARDWARE* device identifies itself as, and what the kernel
> uses to identify which driver should be used to support the device.. There are
> many actual instances where the hardware device has both a USB and PCI variant
> - and only one or the other is actually supported by an in-tree driver.
> And you still haven't told us what driver source you're trying to compile, or
> where it came from.
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kernelnewbies