Kernal/User space change for LE Random Addresses

[Brian Gix <bgix@codeaurora.org>]

One other change that is needed, which I don't really know how to attack 
is remote devices with Random Addresses.  There is at least one team 
here at UPF with a device with a Random Address which cannot be 
connected to with either Vinicius' or the bluetooth-next kernal tips, 
because the connection HCI command only specifies Public Addresses as 
the remote address type.

I am not at all knowledgable about sockets, but I assume that a new 
Socket option needs to be defined that specifies address type.

I can get around this inelegantly by building a secondary kernel which 
hard-codes the address type to Random, and then dual booting into that 
kernel for random address only remote devices.

I would love if someone who knows the bluez socket option handling (both 
kernel and user space) could fix this, otherwise I will try to muddle 
along on my own.


-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum