On Fri, Apr 29, 2011 at 2:41 PM, Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx> wrote: > Hi Johan, > > On Fri, Apr 29, 2011 at 1:56 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: >>> BTW: why this information needs to be exposed through the DeviceFound() signal? >>> It is not used internally in the adapter.c source. >> >> It's useful for pairing UIs. If a device is expected to produce legacy >> pairing when calling CreatePairedDevice the UI can ask the user for the >> PIN *before* calling CreatePairedDevice and thereby eliminate the risk of >> user response timeout locally. > > Maybe this is useful do be documented on doc/device-api.txt? The > LegacyPairing only mentions "This property is useful in the > Adapter.DeviceFound signal to anticipate whether legacy or simple > pairing will occur.", but it is not mentioned *why* the API user might > want to detect legacy pairing devices. On another story, I'm not sure about BR/EDR, but for LE there is a timeout associated with SMP pairing. Would this "anticipate user PIN request" thing be necessary on this case as well? Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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
