From: Mario Limonciello <mario_limonciello@dell.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: [PATCH] Revert "Add API definition for device nodes"
Date: Fri, 07 Aug 2009 13:42:13 -0500 [thread overview]
Message-ID: <4A7C7585.7000409@dell.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 457 bytes --]
This reverts commit 438c23eb400088fbdc830f7287af175559ce9a18.
There is no code in the tree to support these APIs, so they shouldn't
be in the documentation.
---
doc/device-api.txt | 34 ----------------------------------
doc/node-api.txt | 28 ----------------------------
2 files changed, 0 insertions(+), 62 deletions(-)
delete mode 100644 doc/node-api.txt
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-Revert-Add-API-definition-for-device-nodes.patch --]
[-- Type: text/x-patch; name="0001-Revert-Add-API-definition-for-device-nodes.patch", Size: 3113 bytes --]
From 0f2b300557498eb5c23ccf3406901cfcc389a285 Mon Sep 17 00:00:00 2001
From: Mario Limonciello <Mario_Limonciello@Dell.com>
Date: Fri, 7 Aug 2009 13:40:27 -0500
Subject: [PATCH] Revert "Add API definition for device nodes"
This reverts commit 438c23eb400088fbdc830f7287af175559ce9a18.
There is no code in the tree to support these APIs, so they shouldn't
be in the documentation.
---
doc/device-api.txt | 34 ----------------------------------
doc/node-api.txt | 28 ----------------------------
2 files changed, 0 insertions(+), 62 deletions(-)
delete mode 100644 doc/node-api.txt
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 698f9ce..957f0d1 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -71,32 +71,6 @@ Methods dict GetProperties()
Possible errors: org.bluez.Error.NotConnected
- array{object} ListNodes()
-
- Returns list of device node object paths.
-
- Possible errors: org.bluez.Error.InvalidArguments
- org.bluez.Error.Failed
- org.bluez.Error.OutOfMemory
-
- object CreateNode(string uuid)
-
- Creates a persistent device node binding with a
- remote device. The actual support for the specified
- UUID depends if the device driver has support for
- persistent binding. At the moment only RFCOMM TTY
- nodes are supported.
-
- Possible errors: org.bluez.Error.InvalidArguments
- org.bluez.Error.NotSupported
-
- void RemoveNode(object node)
-
- Removes a persistent device node binding.
-
- Possible errors: org.bluez.Error.InvalidArguments
- org.bluez.Error.DoesNotExist
-
Signals PropertyChanged(string name, variant value)
This signal indicates a changed value of the given
@@ -108,14 +82,6 @@ Signals PropertyChanged(string name, variant value)
disconnection to a remote device has been requested.
The actual disconnection will happen 2 seconds later.
- NodeCreated(object node)
-
- Parameter is object path of created device node.
-
- NodeRemoved(object node)
-
- Parameter is object path of removed device node.
-
Properties string Address [readonly]
The Bluetooth device address of the remote device.
diff --git a/doc/node-api.txt b/doc/node-api.txt
deleted file mode 100644
index 7a33dab..0000000
--- a/doc/node-api.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-BlueZ D-Bus Node API description
-********************************
-
-Copyright (C) 2004-2008 Marcel Holtmann <marcel@holtmann.org>
-
-
-Node hierarchy
-==============
-
-Service org.bluez
-Interface org.bluez.Node
-Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX/{node0,...}
-
-Methods dict GetProperties()
-
- Returns all properties for the device node. See the
- properties section for available properties.
-
- Possible Errors: org.bluez.Error.DoesNotExist
- org.bluez.Error.InvalidArguments
-
-Properties string Name [readonly]
-
- The name of the node. For example "rfcomm0".
-
- object Device [readonly]
-
- The object path of the device this node belongs to.
--
1.6.0.4
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
reply other threads:[~2009-08-07 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A7C7585.7000409@dell.com \
--to=mario_limonciello@dell.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox