On Mon, Jan 30, 2012 at 12:05 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > As for the patch itself, we will still need from the wizard to check for > those NULL hints (CreateDevice vs. CreatePairedDevice), or presentation > hints (ICADE and keyboard for example), so the file itself needs to be > made available to the front-ends (and its location exported). > Actually after a few minutes thought, I wondered whether we could handle this by exporting a D-Bus interface from the autopair plugin (like dbus-oob) so you could simply query whether or not a device has presentation hints/needs encryption hints. > For the NULL hints, I would like to see something like > CreatePairedDevice() but that would get whether to pair or not from the > database. > This is another good solution, a plugin callback from here could verify whether or not to pair, etc. > The PIN length hint is also ignored in the current code: > + <device type="audio" oui="00:1A:80:" name="CMT-DH5BT" pin="max:4"/> > Because that's a UI restriction, no? I didn't put any PIN-generation code here, because I'm not entirely sure what the UI for "generate random PIN' should look like or which spec you're following. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? -- 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
