Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-16 Thread Philipp Zabel
On Wed, 2019-10-16 at 15:37 +0200, Paul Kocialkowski wrote: [...] > > > The bottomline is that we have use cases for each of the two set of fields > > > independently, so I feel like this is reason enough to avoid mixing them > > > together. > > > > What do you mean by mixing together? Hardware pa

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-16 Thread Paul Kocialkowski
Hi, I thought I had answered here already, but looks I never sent the email. On Sat 05 Oct 19, 23:21, Tomasz Figa wrote: > On Sat, Oct 5, 2019 at 11:12 PM Paul Kocialkowski > wrote: > > > > On Sat 05 Oct 19, 22:54, Tomasz Figa wrote: > > > On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski > > >

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Paul Kocialkowski
On Sat 05 Oct 19, 23:21, Tomasz Figa wrote: > On Sat, Oct 5, 2019 at 11:12 PM Paul Kocialkowski > wrote: > > > > On Sat 05 Oct 19, 22:54, Tomasz Figa wrote: > > > On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski > > > wrote: > > > > > > > > Hi, > > > > > > > > On Sat 05 Oct 19, 17:22, Tomasz Fig

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Tomasz Figa
On Sat, Oct 5, 2019 at 11:12 PM Paul Kocialkowski wrote: > > On Sat 05 Oct 19, 22:54, Tomasz Figa wrote: > > On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski > > wrote: > > > > > > Hi, > > > > > > On Sat 05 Oct 19, 17:22, Tomasz Figa wrote: > > > > On Fri, Oct 4, 2019 at 6:12 AM Paul Kocialkowsk

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Paul Kocialkowski
On Sat 05 Oct 19, 22:54, Tomasz Figa wrote: > On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski > wrote: > > > > Hi, > > > > On Sat 05 Oct 19, 17:22, Tomasz Figa wrote: > > > On Fri, Oct 4, 2019 at 6:12 AM Paul Kocialkowski > > > wrote: > > > > > > > > Hi, > > > > > > > > On Thu 05 Sep 19, 13:42,

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Tomasz Figa
On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski wrote: > > Hi, > > On Sat 05 Oct 19, 17:22, Tomasz Figa wrote: > > On Fri, Oct 4, 2019 at 6:12 AM Paul Kocialkowski > > wrote: > > > > > > Hi, > > > > > > On Thu 05 Sep 19, 13:42, Philipp Zabel wrote: > > > > To explain why num_ref_idx_active_over

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Paul Kocialkowski
Hi, On Sat 05 Oct 19, 17:22, Tomasz Figa wrote: > On Fri, Oct 4, 2019 at 6:12 AM Paul Kocialkowski > wrote: > > > > Hi, > > > > On Thu 05 Sep 19, 13:42, Philipp Zabel wrote: > > > To explain why num_ref_idx_active_override_flag is not part of the API, > > > describe how the num_ref_idx_l[01]_acti

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-05 Thread Tomasz Figa
On Fri, Oct 4, 2019 at 6:12 AM Paul Kocialkowski wrote: > > Hi, > > On Thu 05 Sep 19, 13:42, Philipp Zabel wrote: > > To explain why num_ref_idx_active_override_flag is not part of the API, > > describe how the num_ref_idx_l[01]_active_minus1 fields and the > > num_ref_idx_l[01]_default_active_min

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-10-03 Thread Paul Kocialkowski
Hi, On Thu 05 Sep 19, 13:42, Philipp Zabel wrote: > To explain why num_ref_idx_active_override_flag is not part of the API, > describe how the num_ref_idx_l[01]_active_minus1 fields and the > num_ref_idx_l[01]_default_active_minus1 fields are used, depending on > whether the decoder parses slice h

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-09-09 Thread Hans Verkuil
On 9/9/19 3:36 PM, Philipp Zabel wrote: > On Mon, 2019-09-09 at 14:43 +0200, Hans Verkuil wrote: >> On 9/9/19 2:27 PM, Philipp Zabel wrote: >>> On Mon, 2019-09-09 at 14:09 +0200, Hans Verkuil wrote: On 9/5/19 1:42 PM, Philipp Zabel wrote: > [...] > @@ -1820,10 +1820,14 @@ enum > v4l2_

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-09-09 Thread Philipp Zabel
On Mon, 2019-09-09 at 14:43 +0200, Hans Verkuil wrote: > On 9/9/19 2:27 PM, Philipp Zabel wrote: > > On Mon, 2019-09-09 at 14:09 +0200, Hans Verkuil wrote: > > > On 9/5/19 1:42 PM, Philipp Zabel wrote: [...] > > > > @@ -1820,10 +1820,14 @@ enum > > > > v4l2_mpeg_video_h264_hierarchical_coding_type

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-09-09 Thread Hans Verkuil
On 9/9/19 2:27 PM, Philipp Zabel wrote: > On Mon, 2019-09-09 at 14:09 +0200, Hans Verkuil wrote: >> On 9/5/19 1:42 PM, Philipp Zabel wrote: >>> To explain why num_ref_idx_active_override_flag is not part of the API, >>> describe how the num_ref_idx_l[01]_active_minus1 fields and the >>> num_ref_idx

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-09-09 Thread Philipp Zabel
On Mon, 2019-09-09 at 14:09 +0200, Hans Verkuil wrote: > On 9/5/19 1:42 PM, Philipp Zabel wrote: > > To explain why num_ref_idx_active_override_flag is not part of the API, > > describe how the num_ref_idx_l[01]_active_minus1 fields and the > > num_ref_idx_l[01]_default_active_minus1 fields are use

Re: [PATCH] media: uapi: h264: clarify num_ref_idx_l[01]_(default_)active fields

2019-09-09 Thread Hans Verkuil
On 9/5/19 1:42 PM, Philipp Zabel wrote: > To explain why num_ref_idx_active_override_flag is not part of the API, > describe how the num_ref_idx_l[01]_active_minus1 fields and the > num_ref_idx_l[01]_default_active_minus1 fields are used, depending on > whether the decoder parses slice headers itse