korg/bluez
0
0
Fork 0
mirror of https://git.kernel.org/pub/scm/bluetooth/bluez.git synced 2024-12-04 17:44:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

More fixes to dbus-api.txt

Browse Source
This commit is contained in:
Johan Hedberg 2006-03-07 21:43:21 +00:00
parent 4cb09e3b00
commit 6a36d0fcf9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
hcid/dbus-api.txt
View File

@ -4,8 +4,8 @@ D-Bus API description for BlueZ
Copyright (C) 2004-2006 Marcel Holtmann <marcel@holtmann.org> Copyright (C) 2004-2006 Marcel Holtmann <marcel@holtmann.org>
Error hierachy Error hierarchy
============== ===============
Interface org.bluez.Error Interface org.bluez.Error
@ -569,7 +569,7 @@ Signals void ModeChanged(string mode)
This signal can also be triggered by low-level HCI This signal can also be triggered by low-level HCI
commands. commands.
void DiscoveryStart() void DiscoveryStarted()
This signal indicates that a device discovery This signal indicates that a device discovery
procedure has been started. procedure has been started.
@ -593,7 +593,7 @@ Signals void ModeChanged(string mode)
void RemoteNameFailed(string address) void RemoteNameFailed(string address)
This signal will be send every time the service daemon This signal will be sent every time the service daemon
tries to resolve a remote and this fails. tries to resolve a remote and this fails.
void RemoteAliasChanged(string address, string alias) void RemoteAliasChanged(string address, string alias)
@ -642,8 +642,8 @@ Methods string Connect(string address, string service)
string ConnectByChannel(string address, byte channel) string ConnectByChannel(string address, byte channel)
This creates a connection to a remote RFCOMM based This creates a connection to a remote RFCOMM based
service. In comparison to Connect a channel number service. In contrast to Connect a channel number is
is needed. needed.
The return value will be the path of the newly The return value will be the path of the newly
creates RFCOMM TTY device (for example /dev/rfcomm0). creates RFCOMM TTY device (for example /dev/rfcomm0).