This is an automatic generated email to let you know that the following patch 
were queued at the 
http://git.linuxtv.org/v4l-utils.git tree:

Subject: v4l2-compliance: update fixme.txt file.
Author:  Hans Verkuil <[email protected]>
Date:    Fri Aug 17 10:36:03 2012 +0200

Several issues in this list have been resolved, so update the file
accordingly.

Signed-off-by: Hans Verkuil <[email protected]>
(cherry picked from commit 1735dffe1bb9499b156e9cfa1141f0e249807e4e)

Signed-off-by: Gregor Jasny <[email protected]>

 utils/v4l2-compliance/fixme.txt |   23 +----------------------
 1 files changed, 1 insertions(+), 22 deletions(-)

---

http://git.linuxtv.org/v4l-utils.git?a=commitdiff;h=89eeb9361fcb52a856a467518a687ee800083544

diff --git a/utils/v4l2-compliance/fixme.txt b/utils/v4l2-compliance/fixme.txt
index 0200430..d7b1d9d 100644
--- a/utils/v4l2-compliance/fixme.txt
+++ b/utils/v4l2-compliance/fixme.txt
@@ -4,31 +4,10 @@ V4L2 specification while writing and testing this compliance 
test tool.
 At some point in time these issues should be resolved, but by placing them
 here they won't be forgotten.
 
-- Should QUERYCAP report capabilities for only the current device node or
-  'system wide'?
-
-- If I set a tuner audio mode to something that is not supported by the 
hardware,
-  should the driver return an error, or silently modify the audio mode, or just
-  accept it?
-
-- G/S_FREQUENCY: this can be used for both receivers and modulators, but if a
-  device has both, then how to I tell the driver that this is the frequency for
-  the modulator instead of the tuner?
-
-- Related question: how do I tell whether a modulator is for TV or FM radio?
-  Spec currently supports modulators for radio only.
-
-- Control documentation is out of date regarding use of class_ctrl 0 and how
+- Control documentation is out of date regarding how
   error_idx should be set for G/S_EXT_CTRLS and for TRY_EXT_CTRLS (which does
   this slightly differently).
 
-- V4L2_FBUF_CAP_SRC_CHROMAKEY: I believe this is defined the wrong way around 
in
-  DocBook.
-
-- define properly V4L2_FBUF_FLAG_PRIMARY and V4L2_FBUF_FLAG_OVERLAY.
-- ditto V4L2_FBUF_CAP_EXTERNOVERLAY: do bytesperline, sizeimage and base need 
to be
-  set or not? Determine for overlay and output overlay.
-
 - RGB pixel formats: endianness issues: two tables in the spec.
 
 - Duplicate controls: V4L2_CID_EXPOSURE (user class) and 
V4L2_CID_EXPOSURE_ABSOLUTE

_______________________________________________
linuxtv-commits mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linuxtv-commits

Reply via email to