diff options
| author | Sreerenj Balachandran <sreerenj.balachandran@intel.com> | 2015-05-27 08:53:17 +0300 |
|---|---|---|
| committer | Xiang, Haihao <haihao.xiang@intel.com> | 2015-06-02 14:29:12 +0800 |
| commit | 4c070b8bae161359fc60afa118baec1a19fde800 (patch) | |
| tree | e2a3288a38ad205722edb816f424d88e8a6ff899 | |
| parent | 4763db1c2133d4e6b92355938ecb6f23a7767b6b (diff) | |
va_dec_hevc.h: Fix the misleading documentation
The slice data buffer should always include the start code prefix.
The comment section of VASliceParameterBufferHEVC is saying that the
accompanying slice_data_buffer should include start code prefix.
But the comment above slice_data_byte_offset is contradicting.
Signed-off-by: Sreerenj Balachandran <sreerenj.balachandran@intel.com>
| -rw-r--r-- | va/va_dec_hevc.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/va/va_dec_hevc.h b/va/va_dec_hevc.h index 860f5ad..d61a283 100644 --- a/va/va_dec_hevc.h +++ b/va/va_dec_hevc.h @@ -264,7 +264,6 @@ typedef struct _VASliceParameterBufferHEVC * there. However, the slice data buffer passed to the hardware is * the original bitstream, thus including any emulation prevention * bytes. - * The slice bit stream may or may not include the start code prefix. */ uint32_t slice_data_byte_offset; /** HEVC syntax element. */ |