Hi,
I noticed that 'CONFIG_ANDROID_BINDER_IPC = m' in package
linux-image-5.19.0-1-arm64 boot/config-5.19.0-1-arm64, while 'CONFIG_ANDROID'
is set to 'n'.
(https://packages.debian.org/bookworm/arm64/linux-image-5.19.0-1-arm64)
However, in the definition file 'drivers/android/Kconfig' there is
Processing control commands:
> tags -1 + fixed-upstream
Bug #919652 [firmware-atheros] ath10k - QCA6174 - Surface Go - missing board
data - fix .bin included extracted form official .msi
Added tag(s) fixed-upstream.
--
919652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919652
Debian Bug
Control: tags -1 + fixed-upstream
On Tue, 19 Jul 2022 23:46:17 +0300 Dmitry Baryshkov
wrote:
> I'd suggest submitting the board files to the ath10k-firmware repo,
> which will then find it's way into linux-firmware.
fwiw this (or, well an update of the existing one) actually happened
already
On maandag 19 september 2022 15:55:13 CEST Diederik de Haas wrote:
> What is needed is finding out which NFC chip(s/set) is being used in your
> device. Assuming it is supported on Linux, it could be as simple as enabling
> a kernel config option.
Right after sending that I found
On maandag 19 september 2022 09:46:41 CEST Oliver Sander wrote:
> I have a ThinkPad X1 Yoga (4th gen). It has an NFC device built in.
> The NFC device appears in the BIOS, and it is enabled there.
> However, I cannot see it from Debian at all. Neither lsusb nor
> lspci show anything ressembling
Package: src:linux
Version: 5.19.6-1
Severity: normal
I have a ThinkPad X1 Yoga (4th gen). It has an NFC device built in.
The NFC device appears in the BIOS, and it is enabled there.
However, I cannot see it from Debian at all. Neither lsusb nor
lspci show anything ressembling an NFC device.
6 matches
Mail list logo
