Hi, Kamil
> Hello,
>
> > From: Jonghun Han [mailto:jonghun@samsung.com]
> > Sent: 06 December 2010 07:57
> >
> > Hi,
> >
> > If MFC(encoder/decoder) has a single node,
> > how to know application's object before VIDIOC_S_FMT calling ?
>
> You're right. No way to know that before.
>
> > VID
Hello,
> From: Jonghun Han [mailto:jonghun@samsung.com]
> Sent: 06 December 2010 07:57
>
> Hi,
>
> If MFC(encoder/decoder) has a single node,
> how to know application's object before VIDIOC_S_FMT calling ?
You're right. No way to know that before.
> VIDIOC_S_CTRL can be called before VIDI
n Han; Laurent Pinchart; jaeryul...@samsung.com;
linux-
> me...@vger.kernel.org
> Subject: Re: RFC: Problem of using v4l2 spec with codec function
>
> Hi all,
> I would side with Laurent on this. Judging by formats seems to be
> enough for this driver and it has great, in my opinion
Hi all,
I would side with Laurent on this. Judging by formats seems to be
enough for this driver and it has great, in my opinion, advantages of
a) not overcomplicating things for applications b) not adding new
pieces to the API...
--
Best regards,
Pawel Osciak
--
To unsubscribe from this list: se
Hi,
Hans Verkuil [hverk...@xs4all.nl] wrote:
> >
> > In two nodes case, application cannot know the feature via
> > VIDIOC_QUERYCAP.
> > Because decoder and encoder return the same CAPABILITY. OUTPUT and
> CAPTURE
> > So application should call VIDIOC_G_FMT to recognize the feature.
>
> The curr
9:17 PM
> To: Jonghun Han
> Cc: 'Laurent Pinchart'; jaeryul...@samsung.com;
linux-media@vger.kernel.org
> Subject: RE: RFC: Problem of using v4l2 spec with codec function
>
>
> >
> > Hi,
> >
> > In two nodes case, application cannot know the fea
Hi Hans,
On Monday 29 November 2010 11:36:03 Hans Verkuil wrote:
> > On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
[snip]
> >> I *think* that what you are saying is that your hardware can have just a
> >> single 'm2m' video instance and so you want to allow the user to switch
> >> betw
27;Hans Verkuil'
>> Cc: jaeryul...@samsung.com; linux-media@vger.kernel.org
>> Subject: RE: RFC: Problem of using v4l2 spec with codec function
>>
>>
>> Laurent Pinchart wrote:
>>
>> > -Original Message-
>> > From: linux-media-ow...
dia-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Jonghun Han
> Sent: Monday, November 29, 2010 8:49 PM
> To: 'Laurent Pinchart'; 'Hans Verkuil'
> Cc: jaeryul...@samsung.com; linux-media@vger.kernel.org
> Subject: RE: RFC: Problem of using v4l2
ia@vger.kernel.org
> Subject: Re: RFC: Problem of using v4l2 spec with codec function
>
> Hi,
>
> > If so, then I think creating a so-called 'private' control for your
> > hardware would be the best way to go. As an example of private controls
> > search for th
> Hi,
>
> On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
>> On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
>> > Hello, everyone.
>> >
>> > When it comes to using v4l2 standard spec, I have a question about
>> that.
>> >
>> > A month ago, Kamil Debski posted second version for the
Hi,
On Monday 29 November 2010 08:34:06 Hans Verkuil wrote:
> On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
> > Hello, everyone.
> >
> > When it comes to using v4l2 standard spec, I have a question about that.
> >
> > A month ago, Kamil Debski posted second version for the driver of a
On Monday, November 29, 2010 00:52:15 Jaeryul Oh wrote:
> Hello, everyone.
>
> When it comes to using v4l2 standard spec, I have a question about that.
>
> A month ago, Kamil Debski posted second version for the driver of a hw video
> codec.
> To be exact, it is decoding function of hw video cod
Hello, everyone.
When it comes to using v4l2 standard spec, I have a question about that.
A month ago, Kamil Debski posted second version for the driver of a hw video
codec.
To be exact, it is decoding function of hw video codec which is called
MFC(Multi Format Codec).
For members not accustom
14 matches
Mail list logo
