Hi Marcel, I'm a little confused about this. Did you mean that if use existing MSFT/AOSP extensions vendor cmd/event to check device has this feature. This way is not meeting your conception, a simple way to tell which RTL device supports the MSFT or AOSP extensions? Thanks. Regards, Hilda -----Original Message----- From: Marcel Holtmann <marcel@xxxxxxxxxxxx> Sent: Thursday, October 7, 2021 11:57 PM To: Hilda Wu <hildawu@xxxxxxxxxxx> Cc: Johan Hedberg <johan.hedberg@xxxxxxxxx>; Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>; linux-bluetooth@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; kai.heng.feng@xxxxxxxxxxxxx; apusaka@xxxxxxxxxxxx; Max Chou <max.chou@xxxxxxxxxxx>; alex_lu@xxxxxxxxxxxxxx; KidmanLee <kidman@xxxxxxxxxxx> 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/mi > crosoft-defined-bluetooth-hci-commands-and-events#hci_vs_msft_read_sup > ported_features > https://source.android.com/devices/bluetooth/hci_requirements#vendor-s > pecific-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 ------Please consider the environment before printing this e-mail.
