Hi Johan, > > @@ -224,6 +225,11 @@ static void hci_init_req(struct hci_dev *hdev, unsigned long opt) > > /* Read Local Supported Features */ > > hci_send_cmd(hdev, HCI_OP_READ_LOCAL_FEATURES, 0, NULL); > > > > + /* Read Local Extended Features */ > > + ext_cp.page = 0x01; > > + hci_send_cmd(hdev, HCI_OP_READ_LOCAL_EXT_FEATURES, sizeof(ext_cp), > > + &ext_cp); > > Since the extended features command is only available from 1.2 onwards I > don't think it's right to unconditionally send it in hci_init_req. > Instead, you should probably be checking for the feature bit in the > (non-extended) feature mask, i.e. in the command complete callback for > HCI_Read_Local_Features and only send the command if the feature bit is > set. exactly and with your work on the management interface, I hope we can get rid of hci_init_req at some point. And then do a proper async and well defined init of the adapter. Especially with things like LE, single mode, AMP, SSP and other factors on the init process, we need to get this fixed once and for all. The AMP init will look fundamentally different from the BR/EDR and init. And so will the LE only init. And it all depends on Bluetooth adapter version and feature bits of course. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
