Hello, V4L2_BUF_FLAG_ERROR flag has been recently introduced. Its meaning is obvious for capture streams - if there is a recoverable stream error the flag is set. This may include corruption in coded stream which results in partially decoded frame, missing stream data, etc. This basically means that the generated data in the buffer may be erroneous. It is somehow different for output streams. There is no (meaningful) data after the buffer is dequeued. Would it be a good idea to use this flag to mark a source buffer that failed to process, because the data it contained was corrupt? By this I mean that a mem2mem device produced no output as it is not possible to set this flag in the capture buffer. And the meaning of this flag would be different. In addition the relationship between source and destination buffers is not always 1:1 for media codecs. This means that lack of destination buffer does not always correspond to an error. Best wishes, -- Kamil Debski Linux Platform Group Samsung Poland R&D Center -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
