Re: [Bluez-devel] D-Bus interfaces

Fredrik Noring
2004-02-11T10:03:18Z

Marcel,

mån 2004-02-09 klockan 11.38 skrev Marcel Holtmann:
> The HCI is well defined in the Bluetooth specification and you can of
> course look at libs2. The source contains all defined HCI commands and
> events for Bluetoth 1.2.

This looks good but many HCI functions are perhaps a bit low level? These
are probably OK:

org.bluetooth.hci.devup
org.bluetooth.hci.devdown
org.bluetooth.hci.devreset
org.bluetooth.hci.devinfo
org.bluetooth.hci.set_pkt_type
org.bluetooth.hci.set_link_policy
org.bluetooth.hci.set_link_mode
org.bluetooth.hci.write_local_name
org.bluetooth.hci.read_local_name
etc.

But these do not appear to be suited for a DBus interface because they deal
with low level things like sockets:

hci_open
hci_close
hci_recv
hci_send_command
hci_send_request
hci_errno
etc.

> We will provide a general and extend interface to the HCI functions,
> so we call it "hci".

Do you mean an extended subset of HCI? I'm not sure I understand, please
explain. What will be omitted and what will be extended?

Thanks,
Fredrik