Hi Johan, > > > > Hijacking the set_powered D-Bus command is the > > > > wrong approach. We need a properly exported adapter_up() function for > > > > this. > > > > > > I believe I tried exporting adapter_up() but it didn't work. > > > > Johan, Luiz, any reason why this would not work. What needs to be done > > to bring up the adapter. Besides calling the ioctl() directly which we > > don't wanna do anymore. > > adapter_up() is more of a callback that's responsible for doing the > necessary initializations *after* adapter has just gone up, so it's not > the right function to call when you want to bring it up (i.e. call the > ioctl). I believe all code paths for bringing the adapter up call set_mode > in src/adapter.c which in turn calls adapter_ops->set_powered (which calls > the ioctl in the case of hciops). > > So having a btd_adapter_set_powered exported to plugins (which is what > Bastien's patch seems to do) makes sense to me in this case. I might > actually need something similar for maemo in order to handle our offline > mode better (maemo specific plugin to catch the MCE offline mode signal > and then call btd_adapter_set_powered). then I leave this with you to export that function correctly. It should be a separate patch anyway. I would disagree with the MCE offline handling as a plugin. First off all, why is it not integrated into RFKILL. Second off all, it could just use RFKILL or RememberPowered=false and change Powered by itself. The listening to offline signal is the wrong design. 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