Hello,
On Thursday, October 08, 2009 11:26 PM Karicheri, Muralidharan wrote:
> > Why not? In a typical camera scenario, application can feed one frame and
> > get two output frames (one
> > for storing and another for sending over email (a lower resolution). I just
> > gave an example.
>
> > Y
f such design? (in
> >terms of mem-2-mem device)
>
> Why not? In a typical camera scenario, application can feed one frame and get
> two output frames (one
> for storing and another for sending over email (a lower resolution). I just
> gave an example.
You gave an example of the Y-type pipeline
Hello,
On Wednesday, October 07, 2009 4:03 PM Karicheri, Muralidharan wrote:
> >How the hardware is actually designed? I see two possibilities:
> >
> >1.
> >[input buffer] --[dma engine]> [resizer1] --[dma]-> [mem output
> >buffer1]
> > \-> [resizer2] --[dma]-> [
Hello,
On Wednesday, October 07, 2009 3:39 PM Karicheri, Muralidharan wrote:
> >> As we have seen in the discussion, this is not a streaming device, rather
> >> a transaction/conversion device which operate on a given frame to get a
> >desired output frame. Each
> >> transaction may have it's own
Marek,
>
>How the hardware is actually designed? I see two possibilities:
>
>1.
>[input buffer] --[dma engine]> [resizer1] --[dma]-> [mem output
>buffer1]
> \-> [resizer2] --[dma]-> [mem output
>buffer2]
>
This is the case.
>2.
>[input buffer] ---[dma engine1]-> [
Marek,
>
>> As we have seen in the discussion, this is not a streaming device, rather
>> a transaction/conversion device which operate on a given frame to get a
>desired output frame. Each
>> transaction may have it's own set of configuration context which will be
>applied to the hardware
>> befor
Hello,
On Tuesday, October 06, 2009 6:12 PM Hiremath, Vaibhav wrote:
> > On Monday, October 05, 2009 8:27 PM Hiremath, Vaibhav wrote:
> >
> > > > > [Hiremath, Vaibhav] IMO, this implementation is not streaming
> > > > model, we are trying to fit mem-to-mem
> > > > > forcefully to streaming.
> > >
gt; Szyprowski
> Subject: RE: Mem2Mem V4L2 devices [RFC]
>
> Hello,
>
> On Monday, October 05, 2009 8:27 PM Hiremath, Vaibhav wrote:
>
> > > > [Hiremath, Vaibhav] IMO, this implementation is not streaming
> > > model, we are trying to fit mem-to-mem
> >
Hi,
On Tue, 2009-10-06 at 08:23 +0200, Marek Szyprowski wrote:
> Hello,
>
> On Monday, October 05, 2009 8:27 PM Hiremath, Vaibhav wrote:
>
> > > > [Hiremath, Vaibhav] IMO, this implementation is not streaming
> > > model, we are trying to fit mem-to-mem
> > > > forcefully to streaming.
> > >
>
Hello,
On Monday, October 05, 2009 10:02 PM Karicheri, Muralidharan wrote:
> There is another use case where there are two Resizer hardware working om the
> same input frame and
> give two different output frames of different resolution. How do we handle
> this using the one video
> device appr
Hello,
On Monday, October 05, 2009 8:27 PM Hiremath, Vaibhav wrote:
> > > [Hiremath, Vaibhav] IMO, this implementation is not streaming
> > model, we are trying to fit mem-to-mem
> > > forcefully to streaming.
> >
> > Why this does not fit streaming? I see no problems with streaming
> > over mem2
Hello,
On October 06, 2009 12:31 AM Karicheri, Muralidharan wrote:
> Are we constrained to use the QBUF/DQBUF/STREAMON/STREAMOFF model for this
> specific device (memory to
> memory)? What about adding new IOCTLs that can be used for this specific
> device type that possibly can
> simplify the
sz Fujak; Pawel Osciak
> Subject: RE: Mem2Mem V4L2 devices [RFC]
>
> > -Original Message-
> > From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
> > Sent: Monday, October 05, 2009 7:26 PM
> > To: Hiremath, Vaibhav; linux-media@vger.kernel.org
> >
:iiva...@mm-sol.com]
>Sent: Monday, October 05, 2009 4:14 PM
>To: Karicheri, Muralidharan
>Cc: Marek Szyprowski; linux-media@vger.kernel.org;
>kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak
>Subject: RE: Mem2Mem V4L2 devices [RFC]
>
>Hi,
>
>
>On Mon, 2009-10-05 at 1
>>
>> Ivan,
>>
>> There is another use case where there are two Resizer hardware working on
>the same input frame and give two different output frames of different
>resolution. How do we handle this using the one video device approach you
>> just described here?
>
> what is the difference?
>
>- yo
Hi,
On Mon, 2009-10-05 at 15:02 -0500, Karicheri, Muralidharan wrote:
>
> >>
> >> 1. How to set different color space or size for input and output buffer
> >> each? It could be solved by adding a set of ioctls to get/set source
> >> image format and size, while the existing v4l2 ioctls would on
>>
>> 1. How to set different color space or size for input and output buffer
>> each? It could be solved by adding a set of ioctls to get/set source
>> image format and size, while the existing v4l2 ioctls would only refer
>> to the output buffer. Frankly speaking, we don't like this idea.
>
>I
vger.kernel.org;
> kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak
> Subject: RE: Mem2Mem V4L2 devices [RFC]
>
> On Tue, 2009-10-06 at 00:31 +0530, Hiremath, Vaibhav wrote:
> > > -Original Message-
> > > From: Ivan T. Ivanov [mailto:iiva...@mm-sol.com]
&
ger.kernel.org;
> > kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak
> > Subject: RE: Mem2Mem V4L2 devices [RFC]
> >
> >
>
> > > > > > last thing which should be done is to QBUF 2 buffers and
> > call
> > > > > > STREAMON.
> > >
> -Original Message-
> From: Ivan T. Ivanov [mailto:iiva...@mm-sol.com]
> Sent: Tuesday, October 06, 2009 12:27 AM
> To: Hiremath, Vaibhav
> Cc: Marek Szyprowski; linux-media@vger.kernel.org;
> kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak
> Subject: RE: Mem2
linux-media@vger.kernel.org
> > Cc: kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak; Marek
> > Szyprowski
> > Subject: RE: Mem2Mem V4L2 devices [RFC]
> >
> > Hello,
> >
> > On Monday, October 05, 2009 7:59 AM Hiremath, Vaibhav wrote:
> >
> >
gt; Szyprowski
> Subject: RE: Mem2Mem V4L2 devices [RFC]
>
> Hello,
>
> On Monday, October 05, 2009 7:59 AM Hiremath, Vaibhav wrote:
>
> > -Original Message-
> > From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of
> -Original Message-
> From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
> Sent: Monday, October 05, 2009 7:26 PM
> To: Hiremath, Vaibhav; linux-media@vger.kernel.org
> Cc: kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak; Marek
> Szyprowski
> Subject: RE:
Hi,
On Mon, 2009-10-05 at 15:54 +0200, Marek Szyprowski wrote:
> Hello,
>
> On Friday, October 02, 2009 6:25 PM Ivan T. Ivanov wrote:
>
> > On Fri, 2009-10-02 at 13:45 +0200, Marek Szyprowski wrote:
> > > Hello,
> > >
> > > During the V4L2 mini-summit and the Media Controller RFC discussion on
n T. Ivanov; Marek Szyprowski
> Cc: linux-media@vger.kernel.org; kyungmin.p...@samsung.com; Tomasz Fujak;
> Pawel Osciak
> Subject: RE: Mem2Mem V4L2 devices [RFC]
>
>
> > -Original Message-
> > From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> >
Hello,
On Monday, October 05, 2009 7:43 AM Hiremath, Vaibhav wrote:
> In terms of V4L2 framework such device would be both video
> > sink
> > and source at the same time. The main problem is how the video nodes
> > (/dev/videoX) should be assigned to such a device.
> >
> > The simplest way of imp
Hello,
On Friday, October 02, 2009 6:25 PM Ivan T. Ivanov wrote:
> On Fri, 2009-10-02 at 13:45 +0200, Marek Szyprowski wrote:
> > Hello,
> >
> > During the V4L2 mini-summit and the Media Controller RFC discussion on
> > Linux Plumbers 2009 Conference a mem2mem video device has been mentioned
> >
asz
> Fujak; Pawel Osciak
> Subject: Re: Mem2Mem V4L2 devices [RFC]
>
>
> Hi Marek,
>
>
> On Fri, 2009-10-02 at 13:45 +0200, Marek Szyprowski wrote:
> > Hello,
> >
> > image format and size, while the existing v4l2 ioctls would only
> refer
> > to
awel Osciak; Marek
> Szyprowski
> Subject: Mem2Mem V4L2 devices [RFC]
>
> Hello,
>
> During the V4L2 mini-summit and the Media Controller RFC discussion
> on
> Linux Plumbers 2009 Conference a mem2mem video device has been
> mentioned
> a few times (usually in a context of
Hi Marek,
On Fri, 2009-10-02 at 13:45 +0200, Marek Szyprowski wrote:
> Hello,
>
> During the V4L2 mini-summit and the Media Controller RFC discussion on
> Linux Plumbers 2009 Conference a mem2mem video device has been mentioned
> a few times (usually in a context of a 'resizer device' which
Hello,
During the V4L2 mini-summit and the Media Controller RFC discussion on
Linux Plumbers 2009 Conference a mem2mem video device has been mentioned
a few times (usually in a context of a 'resizer device' which might be a
part of Camera interface pipeline or work as a standalone device). We
31 matches
Mail list logo
