On Fri, 2015-07-24 at 00:32 +0200, Szymon Janc wrote: > Hi Bastien, > > On Tuesday 07 July 2015 16:14:00 Bastien Nocera wrote: > > Add btd_request_authorization_cable_configured() function to allow > > cable configured devices to ask the user straight away about > > whether the > > device should be allowed to connect to the computer. > > > > This allows us to ask the user at the time of the USB connection > > and > > initial setup, rather than when the first Bluetooth connection is > > made. > > I'd also add a note to doc/agent-api.txt that this can be called also > for not > connected devices under some circumstances (and see how it fits). As I mentioned on IRC, I'm happy to do that if the rest of the patch is deemed fine. > What bothers me is that now bluetoothd will send AuthorizeService > request for > device that is not connected (and authorizing will not result in > connection). That's not what that patch does though, this patch just adds wiring to do that... > And this was explicitly checked against before this patch. It's still checked, just not through the sixaxis plugin. That's the only entry point that disables that check. <snip> > > Also in general I'd prefer to use sixaxis instead of cable in names. > Mainly > for consistency with other core sixaxis specific code. It's not sixaxis specific, and could be used by any cable pairing, where the device is useful both when plugged in and then through BT. Johan is the one that preferred cable rather than sixaxis, as the method isn't specific to sixaxis but could be used for other devices too. -- 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
