---

yaml --- r: 320639 b: refs/heads/master c: a1367f1 h: refs/heads/master i: 320637: 4b9fff6 320635: 73aa208 320631: c10a147 320623: 66c4458 320607: c02051b 320575: ca1c800 320511: b066fb5 v: v3
git-mirror · Jul 30, 2012 · 4eae4a9 · 4eae4a9
1 parent 5891ff6
commit 4eae4a9
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 1 deletion.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: f0476a83d61a8004eb535a0b65721ca405421fe8
+refs/heads/master: a1367f1b260d29e9b9fb20d8e2f39f1e74fa6c3b
diff --git a/trunk/Documentation/feature-removal-schedule.txt b/trunk/Documentation/feature-removal-schedule.txt
@@ -576,3 +576,17 @@ Why:	The regular V4L2 selections and the subdev selection API originally
 	any instabilities in the user space interface. After few cycles these
 	backward compatibility definitions will be removed.
 Who:	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
+
+----------------------------
+
+What:	Using V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags
+	to indicate a V4L2 memory-to-memory device capability
+When:	3.8
+Why:	New drivers should use new V4L2_CAP_VIDEO_M2M capability flag
+	to indicate a V4L2 video memory-to-memory (M2M) device and
+	applications can now identify a M2M video device by checking
+	for V4L2_CAP_VIDEO_M2M, with VIDIOC_QUERYCAP ioctl. Using ORed
+	V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags for M2M
+	devices is ambiguous and may lead, for example, to identifying
+	a M2M device as a video	capture or output device.
+Who:	Sylwester Nawrocki <s.nawrocki@samsung.com>