Hi Jukka, > here is first version of BT LE 6LoWPAN functionality but using > connection oriented channels instead of fixed channel one. > > At the moment, the initial configuration needs to be done manually. > So in the slave device say: > # echo node > /sys/kernel/debug/bluetooth/hci0/6lowpan_role > # echo Y > /sys/kernel/debug/bluetooth/hci0/6lowpan > # hciconfig hci0 leadv > > And in the master device say: > # echo Y > /sys/kernel/debug/bluetooth/hci0/6lowpan > # hcitool lecc <slave-addr> my current idea of providing an mgmt API for networking is to introduce HCI_CHANNEL_NETWORK and use a network specific mgmt API on that socket. This is something to think about. We could extend it to BNEP/PAN as well where we handle the whole connection logic inside the kernel. That way you can easily enable/disable PAN or 6loWPAN. bluetoothd or even an external 6loWPAN daemon could deal with connection establishment and acceptance. However more importantly this could be easily confined into bluetooth_network.ko at some point in the future and then automatically loaded via bt-chan-4 module aliases. Similar to how we load RFCOMM module via bt-proto-3 when accessing the socket. Alternative we can create a mgmt subcommand API and then load modules via bt-mgmt-x type of handling once accessing subcommands. Regards Marcel -- 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
