[pulseaudio-discuss] [PATCH 19/30] PROTOCOL: Don't forbid bidirectional nodes
Tanu Kaskinen
tanu.kaskinen at linux.intel.com
Thu Jan 16 07:02:45 PST 2014
We will probably at some point have bidirectional nodes (for example,
a sink node that also includes the monitor), so it's not a good idea
to forbid that case in the protocol documentation.
---
PROTOCOL | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/PROTOCOL b/PROTOCOL
index 08e4583..31307d7 100644
--- a/PROTOCOL
+++ b/PROTOCOL
@@ -376,8 +376,7 @@ GET_NODE_INFO reply parameters:
pa_direction_t direction
The index must not be PA_INVALID_INDEX. The name must not be NULL or empty. The
-description must not be NULL or empty. The direction must be either OUTPUT or
-INPUT, not both.
+description must not be NULL or empty.
GET_NODE_INFO_LIST reply parameters are otherwise the same as with
GET_NODE_INFO, but the parameter list is repeated for each node.
--
1.8.3.1
More information about the pulseaudio-discuss
mailing list