[libdc1394-devel] [RFC PATCH] ieee1394: document status of userspace ABIs

[Stefan R. <st...@s5...>]

Signed-off-by: Stefan Richter <st...@s5...>
---

See linux/Documentation/ABI/README for levels of ABI stability.
http://lxr.linux.no/source/Documentation/ABI/

raw1394 does not have to be in ABI/stable because we maintain stability
via libraw1394.  Alas video1394 has always been exposed for direct usage
by application developers but there is at least libdc1394 as low-level
abstraction for IIDC applications.

Please comment and correct me where I'm wrong.


 Documentation/ABI/testing/raw1394   |    7 +++++++
 Documentation/ABI/testing/video1394 |    9 +++++++++
 2 files changed, 16 insertions(+)

Index: linux/Documentation/ABI/testing/raw1394
===================================================================
--- /dev/null
+++ linux/Documentation/ABI/testing/raw1394
@@ -0,0 +1,7 @@
+What:		raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire)
+Contact:	<lin...@li...>
+
+Description:	Never access raw1394 directly from application programs.
+		Use libraw1394 or/and higher-level libraries.
+
+Users:		libraw1394 <lin...@li...>
Index: linux/Documentation/ABI/testing/video1394
===================================================================
--- /dev/null
+++ linux/Documentation/ABI/testing/video1394
@@ -0,0 +1,9 @@
+What:		video1394 (a.k.a. "OHCI-1394 Video support" for FireWire)
+Contact:	<lin...@li...>
+
+Description:	Direct access to video1394 is discouraged.
+		Use libdc1394 or/and higher-level libraries.
+
+Users:		libdc1394 <lib...@li...>
+		dvconnect (can be replaced by dvgrab which does not use video1394)
+		potentially lots of unknown in-house applications


-- 
Stefan Richter
-=====-=-=== --== ==--=
http://arcgraph.de/sr/