[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <065AC802-1C20-42F0-9B2F-24F2B2698B90@holtmann.org>
Date: Thu, 7 Oct 2021 17:56:41 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Hilda Wu <hildawu@...ltek.com>
Cc: Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kai.heng.feng@...onical.com" <kai.heng.feng@...onical.com>,
"apusaka@...omium.org" <apusaka@...omium.org>,
Max Chou <max.chou@...ltek.com>,
"alex_lu@...lsil.com.cn" <alex_lu@...lsil.com.cn>,
KidmanLee <kidman@...ltek.com>
Subject: Re: [PATCH] Bluetooth: btrtl: Ask ic_info to drop firmware
Hi Hilda,
> The MSFT extension has a HCI_VS_MSFT_Read_Supported_Features command. The AOSP extension has a read capability cmd too.
> https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/microsoft-defined-bluetooth-hci-commands-and-events#hci_vs_msft_read_supported_features
> https://source.android.com/devices/bluetooth/hci_requirements#vendor-specific-capabilities
> If commands did not support, the controller should feedback event status as Unknown HCI Command (0x01).
> We can go on this way.
I am not doing trial-and-error programming here. I rather better disable any extensions for Realtek devices altogether.
Regards
Marcel
Powered by blists - more mailing lists