Re: [PATCH 04/12] media: coda: allocate internal framebuffers separately from v4l2 buffers

On 28 August 2012 10:40, Philipp Zabel wrote: > Hi Javier, > > Am Dienstag, den 28.08.2012, 09:50 +0200 schrieb javier Martin: >> Hi Phillip, >> I see you are trying a cleaner approach for reference and reconstructed >> frames. >> > -#define CODA_OUTPUT_BUFS 4 >> > -#define CODA_CAPTURE_BUF

Re: [PATCH 04/12] media: coda: allocate internal framebuffers separately from v4l2 buffers

Hi Javier, Am Dienstag, den 28.08.2012, 09:50 +0200 schrieb javier Martin: > Hi Phillip, > I see you are trying a cleaner approach for reference and reconstructed > frames. > > -#define CODA_OUTPUT_BUFS 4 > > -#define CODA_CAPTURE_BUFS 2 > > +#define CODA_MAX_FRAMEBUFFERS 2 > > Accor

Re: [PATCH 04/12] media: coda: allocate internal framebuffers separately from v4l2 buffers

On 28 August 2012 09:50, javier Martin wrote: > Hi Phillip, > I see you are trying a cleaner approach for reference and reconstructed > frames. > > On 24 August 2012 18:17, Philipp Zabel wrote: >> Some codecs running on CODA need internal framebuffers for reference and >> reconstructed frames. A

Re: [PATCH 04/12] media: coda: allocate internal framebuffers separately from v4l2 buffers

Hi Phillip, I see you are trying a cleaner approach for reference and reconstructed frames. On 24 August 2012 18:17, Philipp Zabel wrote: > Some codecs running on CODA need internal framebuffers for reference and > reconstructed frames. Allocate them separately, and do not use the input > vb2_buf

[PATCH 04/12] media: coda: allocate internal framebuffers separately from v4l2 buffers

Some codecs running on CODA need internal framebuffers for reference and reconstructed frames. Allocate them separately, and do not use the input vb2_buffers: those will be handed off to userspace regularly, and there is no way to signal to the CODA which of the registered framebuffers are off limi