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
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.
VIDIOC_S_CTRL can be
...@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, advantages of
a) not overcomplicating things
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:
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 current V4L API
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 hw
video
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 hw
: RFC: Problem of using v4l2 spec with codec function
Hi,
snip
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 the V4L2_CID_MPEG_CX2341X_BASE define in videodev2.h.
I would rely
[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 spec with codec function
Laurent Pinchart
...@samsung.com; linux-media@vger.kernel.org
Subject: Re: RFC: Problem of using v4l2 spec with codec function
Hi,
snip
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
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
between the
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 feature via
VIDIOC_QUERYCAP.
Because decoder and encoder return the same
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 codec
13 matches
Mail list logo
