On 05/07/14 13:26, Divneil Wadhawan wrote:
> Hi Hans
>
>> Hmm, I always wondered when this would happen.
>
> :)
>
>
>> In theory we could make the number of maximum frames driver specific, but
>> it would be more trouble than it's worth at the moment IMHO.
>
> You mean to say adding a new field in struct vb2_queue.
No, just add a VB2_MAX_FRAME define and use that everywhere in vb2 and any
driver depending on vb2 instead of VIDEO_MAX_FRAME.
The VIDEO_MAX_FRAME define is used for vb2 internal array sizes, and those
need to be increased. So replacing VIDEO_MAX_FRAME by VB2_MAX_FRAME is the
easiest approach.
Regards,
Hans
> Hmm, I will nod yes, because, the requirement for me is no more than 64.
>
>
>> Which driver are you using? Is it something that you or someone else is
>> likely to upstream to the linux kernel?
> It's again TSMUXER. There are new data types defined, and some other stuff.
>
> I cannot commit on this, however, I am currently seeing this driver.
>
>
> Regards,
>
> Divneil
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
