Hi Vinicius, On Thu, Oct 25, 2012, Vinicius Costa Gomes wrote: > > On Thu, Oct 25, 2012, Johan Hedberg wrote: > > > This will need some more thinking. We could add a new mgmt command for > > > that, or if you wanna go crazy why not map this to the L2CAP socket > > > interface's connect() system call. I.e. if LE GAP is in peripheral mode > > > instead of doing HCI_LE_Create_Connection or just failing with "not > > > allowed" a socket connect() would simply trigger directed advertising to > > > the device in question and deliver the successful connection in the same > > > way as a central role triggered connect would do (unless we time out > > > waiting for the remote device to connect). Now that I think of this > > > second option it actually sounds quite natural and not so crazy after > > > all :) > > > > There's on problem with this though: we'd still be undirected > > connectable between doing mgmt_set_le(peripheral) and issuing the socket > > connect(). So maybe we might need to introduce a mgmt_set_le_connectable > > command and a "le-connectable" setting after all (that could only be set > > in peripheral mode). > > Why not sending undirected connectable events when there's an active > listen()? But we always have that, don't we? (the GATT server socket). Or are you saying that bluetoothd could close its GATT server socket before switching to peripheral mode and that would ensure that the kernel doesn't enable connectable advertising? 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
