Hi Marcel, On Fri, Oct 31, 2014, Marcel Holtmann wrote: > > So, hardware error seems the best way to warn host stack about the H5 controller > > reset. > > I am actually fine with doing it this way. > > > Regarding the "upper stack", I know that Bluedroid restarts on hardware error, but > > I ignore the Bluez behavior. > > This is something we need to fix then. First and foremost this has to > work with the Bluetooth subsystem in the kernel as well and not just a > stack on top of HCI User Channel. Agreed. I've now applied this patch to bluetooth-next so we can continue towards making the higher layers do the right thing as well. 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
