Hi Marcel, On Tue, Dec 23, 2014, Marcel Holtmann wrote: > When controllers set the HCI_QUIRK_INVALID_BDADDR flag, it is required > by userspace to program a valid public Bluetooth device address into > the controller before it can be used. > > After successful address configuration, the internal state changes and > the controller runs the complete initialization procedure. However one > small difference is that this is no longer the HCI_SETUP stage. The > HCI_SETUP stage is only valid during initial controller setup. In this > case the stack runs the initialization as part of the HCI_CONFIG stage. > > The controller version information, default name and supported commands > are only stored during HCI_SETUP. While these information are static, > they are not read initially when HCI_QUIRK_INVALID_BDADDR is set. So > when running in HCI_CONFIG state, these information need to be updated > as well. > > This especially impacts Bluetooth 4.1 and later controllers using > extended feature pages and second event mask page. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > Cc: stable@xxxxxxxxxxxxxxx # 3.17.x > --- > net/bluetooth/hci_event.c | 9 ++++++--- > 1 file changed, 6 insertions(+), 3 deletions(-) Applied to bluetooth.git. Thanks. Johan -- 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
