Hi, On Mon, Aug 08, 2011, Anderson Lizardo wrote: > On Mon, Aug 8, 2011 at 10:59 AM, VISHWANATH KM <a21174@xxxxxxxxxxxx> wrote: > >> I think you have two options: > >> > >> 1) Always use CreateDevice(). Then if you want to issue SMP pairing, > >> you can change the BT_IO_SECLEVEL when connection with bt_io_connect() > >> (I haven't tested this lately, but I remember it used to work). > >> > >> 2) Extend the kernel Management API to allow Features Exchange. See > >> doc/mgmt-api.txt for the existing commands, to have an idea on how it > >> works (I recommend first sending an API proposal here to the list). > > > > Option 2 sounds better, where we use CreatePairedDevice and after the LE ACL > > is established we can do LE Read Remote features, (similar to what we do for > > BR i.e we do HCI Read Remote features in conn complete ) and if Encryption > > feature bit is set then we trigger SMP else we don't, pls let me know if any > > comments, if this sounds ok then i will mail the changes to this maillist > > for further review > > Let's hear others opinions. Johan, Marcel, Gustavo? To me it seems pretty clear from the core spec that this is purely about Link Layer (i.e. controller side) behavior which doesn't tell you anything about the host side capabilities. I also don't see any corresponding write command which further confirms that this is not something dependent on host-side features. I.e. I don't think you can use this to conclude anything about SMP support on the remote side. 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
