Em 30-05-2011 04:14, Hans Verkuil escreveu:
> On Sunday, May 29, 2011 16:55:38 Mauro Carvalho Chehab wrote:
>> Em 29-05-2011 10:30, Hans de Goede escreveu:
>> IMO, we should be reviewing this policy, for example, to name video output
>> devices as "video_out", and webcams as "webcam", and let udev
Em 30-05-2011 03:54, Hans Verkuil escreveu:
> On Sunday, May 29, 2011 14:11:05 Mauro Carvalho Chehab wrote:
>> Em 29-05-2011 08:19, Hans Verkuil escreveu:
>>> It's what you expect to see in an application: a list of USB/PCI/Platform
>>> devices to choose from.
>>
>> A missing function is to return
Em 30-05-2011 03:34, Hans Verkuil escreveu:
> On Sunday, May 29, 2011 14:11:05 Mauro Carvalho Chehab wrote:
>> In other words, for event/input devices, if someone needs to have more than
>> one IR, each directed to a different set of windows/applications, he will
>> need to manually configure what
On Sunday, May 29, 2011 16:55:38 Mauro Carvalho Chehab wrote:
> Em 29-05-2011 10:30, Hans de Goede escreveu:
> > Hi,
> >
> > On 05/29/2011 03:08 PM, Mauro Carvalho Chehab wrote:
> >> Em 29-05-2011 08:54, Hans de Goede escreveu:
> >>> Hi,
> >>>
> >>> On 05/29/2011 01:19 PM, Hans Verkuil wrote:
> >>
On Sunday, May 29, 2011 14:11:05 Mauro Carvalho Chehab wrote:
> Em 29-05-2011 08:19, Hans Verkuil escreveu:
> >> Each device type that is known by the API is defined inside enum
> >> device_type,
> >> currently defined as:
> >>
> >>enum device_type {
> >>UNKNOWN = 65535,
> >>
On Sunday, May 29, 2011 14:11:05 Mauro Carvalho Chehab wrote:
> Em 29-05-2011 08:19, Hans Verkuil escreveu:
> >> Each device type that is known by the API is defined inside enum
> >> device_type,
> >> currently defined as:
> >>
> >>enum device_type {
> >>UNKNOWN = 65535,
> >>
Em 29-05-2011 10:30, Hans de Goede escreveu:
> Hi,
>
> On 05/29/2011 03:08 PM, Mauro Carvalho Chehab wrote:
>> Em 29-05-2011 08:54, Hans de Goede escreveu:
>>> Hi,
>>>
>>> On 05/29/2011 01:19 PM, Hans Verkuil wrote:
Hi Mauro,
Thanks for the RFC! Some initial comments below. I'll hop
Em 29-05-2011 09:11, Mauro Carvalho Chehab escreveu:
> Em 29-05-2011 08:19, Hans Verkuil escreveu:
>>> enum device_type {
>>> UNKNOWN = 65535,
>>> NONE= 65534,
>>> MEDIA_V4L_VIDEO = 0,
>>
>> Can you add MEDIA_V4L_RADIO as well? And MEDIA_V4L_SUBDEV too.
Hi,
On 05/29/2011 03:08 PM, Mauro Carvalho Chehab wrote:
Em 29-05-2011 08:54, Hans de Goede escreveu:
Hi,
On 05/29/2011 01:19 PM, Hans Verkuil wrote:
Hi Mauro,
Thanks for the RFC! Some initial comments below. I'll hope to do some more
testing and reviewing in the coming week.
c) get_no
Em 29-05-2011 08:54, Hans de Goede escreveu:
> Hi,
>
> On 05/29/2011 01:19 PM, Hans Verkuil wrote:
>> Hi Mauro,
>>
>> Thanks for the RFC! Some initial comments below. I'll hope to do some more
>> testing and reviewing in the coming week.
>>
>
>
>
>>> c) get_not_associated_device: Returns the ne
Em 29-05-2011 08:47, Andy Walls escreveu:
> Hans Verkuil wrote:
>>> Each device type that is known by the API is defined inside enum
>> device_type,
>>> currently defined as:
>>>
>>> enum device_type {
>>> UNKNOWN = 65535,
>>> NONE= 65534,
>>> MEDIA_V4L_
Em 29-05-2011 08:19, Hans Verkuil escreveu:
>> Each device type that is known by the API is defined inside enum device_type,
>> currently defined as:
>>
>> enum device_type {
>> UNKNOWN = 65535,
>> NONE= 65534,
>> MEDIA_V4L_VIDEO = 0,
>
> Can you add
Hi,
On 05/29/2011 01:19 PM, Hans Verkuil wrote:
Hi Mauro,
Thanks for the RFC! Some initial comments below. I'll hope to do some more
testing and reviewing in the coming week.
c) get_not_associated_device: Returns the next device not associated with
an specifi
Hans Verkuil wrote:
>Hi Mauro,
>
>Thanks for the RFC! Some initial comments below. I'll hope to do some
>more
>testing and reviewing in the coming week.
>
>On Sunday, May 29, 2011 03:01:43 Mauro Carvalho Chehab wrote:
>> Em 28-05-2011 13:20, Mauro Carvalho Chehab escreveu:
>> > Em 28-05-2011 12:2
Hi Mauro,
Thanks for the RFC! Some initial comments below. I'll hope to do some more
testing and reviewing in the coming week.
On Sunday, May 29, 2011 03:01:43 Mauro Carvalho Chehab wrote:
> Em 28-05-2011 13:20, Mauro Carvalho Chehab escreveu:
> > Em 28-05-2011 12:24, Hans Verkuil escreveu:
> >>
Em 28-05-2011 13:20, Mauro Carvalho Chehab escreveu:
> Em 28-05-2011 12:24, Hans Verkuil escreveu:
>> But I would really like to see an RFC with a proposal of the API and how
>> it is to be used. Then after an agreement has been reached the library can
>> be modified accordingly and we can release
Em 28-05-2011 12:24, Hans Verkuil escreveu:
> But I would really like to see an RFC with a proposal of the API and how
> it is to be used. Then after an agreement has been reached the library can
> be modified accordingly and we can release it.
Ok, that's the RFC for the API. The code is already c
Em 28-05-2011 12:24, Hans Verkuil escreveu:
> On Saturday, May 28, 2011 14:17:25 Mauro Carvalho Chehab wrote:
>> Em 26-05-2011 03:53, Hans Verkuil escreveu:
>>> On Tuesday, May 24, 2011 16:57:22 Devin Heitmueller wrote:
On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
> On Monday, May
On Saturday, May 28, 2011 14:17:25 Mauro Carvalho Chehab wrote:
> Em 26-05-2011 03:53, Hans Verkuil escreveu:
> > On Tuesday, May 24, 2011 16:57:22 Devin Heitmueller wrote:
> >> On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
> >>> On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
Em 28-05-2011 10:01, Rémi Denis-Courmont escreveu:
> Le samedi 28 mai 2011 15:44:52 Mauro Carvalho Chehab, vous avez écrit :
>>> int libv4l2_get_associated_devive(int fd, enum
>>> libv4l2_associated_device_types type, ...); Where fd is the fd of an
>>> open /dev/video node, and ... is a param throu
Em 28-05-2011 09:55, Rémi Denis-Courmont escreveu:
> Le mardi 24 mai 2011 17:09:45 Mauro Carvalho Chehab, vous avez écrit :
>> If we do that, then all other places where the association between an alsa
>> device and a video4linux node is needed will need to copy it, and we'll
>> have a fork. Also,
Em 28-05-2011 09:44, Mauro Carvalho Chehab escreveu:
>> Anyways I think we're are currently
>> doing this the wrong way up. We should first discuss what such an API
>> should look like and then implement it. Hopefully we can re-use a lot
>> of the existing code when we do this, but I think it is b
Le samedi 28 mai 2011 15:44:52 Mauro Carvalho Chehab, vous avez écrit :
> > int libv4l2_get_associated_devive(int fd, enum
> > libv4l2_associated_device_types type, ...); Where fd is the fd of an
> > open /dev/video node, and ... is a param through which the device gets
> > returned (I guess a char
Le mardi 24 mai 2011 17:09:45 Mauro Carvalho Chehab, vous avez écrit :
> If we do that, then all other places where the association between an alsa
> device and a video4linux node is needed will need to copy it, and we'll
> have a fork. Also, we'll keep needing it at v4l-utils, as it is now needed
Em 24-05-2011 12:55, Hans de Goede escreveu:
> Hi,
>
> On 05/24/2011 04:09 PM, Mauro Carvalho Chehab wrote:
>> Em 24-05-2011 04:21, Hans de Goede escreveu:
>>> Hi,
>>
>>> My I suggest that we instead just copy over the single get_media_devices.c
>>> file to xawtv, and not install the not so much a
Hi,
On 05/28/2011 02:17 PM, Mauro Carvalho Chehab wrote:
Em 26-05-2011 03:53, Hans Verkuil escreveu:
On Tuesday, May 24, 2011 16:57:22 Devin Heitmueller wrote:
On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
Due to the alsa
Em 26-05-2011 03:53, Hans Verkuil escreveu:
> On Tuesday, May 24, 2011 16:57:22 Devin Heitmueller wrote:
>> On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
>>> On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
Due to the alsa detection code that I've added at libv4l2util (at
Em 24-05-2011 11:57, Devin Heitmueller escreveu:
> On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
>> On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
>>> Due to the alsa detection code that I've added at libv4l2util (at
>>> v4l2-utils)
>>> during the weekend, I decided to add a
On Tuesday, May 24, 2011 16:57:22 Devin Heitmueller wrote:
> On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
> > On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
> >> Due to the alsa detection code that I've added at libv4l2util (at
> >> v4l2-utils)
> >> during the weekend, I de
On Tue, May 24, 2011 at 1:26 PM, Emil Meier wrote:
> Are there mechanisms for device-locking in the v4l api? With my 2 hybrid
> saa7134 cards I have observed exactly this issues in Mythtv and also in xawtv
> and kaffeine
> At the moment I disable one device via additional card definitions an
--- On Tue, 24/5/11, Devin Heitmueller wrote:
> From: Devin Heitmueller
> Subject: Re: [ANNOUNCE] experimental alsa stream support at xawtv3
> To: "Hans Verkuil"
> Cc: "Mauro Carvalho Chehab" , "Linux Media Mailing List"
>
> Date: Tuesday, 24
Hi,
On 05/24/2011 04:09 PM, Mauro Carvalho Chehab wrote:
Em 24-05-2011 04:21, Hans de Goede escreveu:
Hi,
My I suggest that we instead just copy over the single get_media_devices.c
file to xawtv, and not install the not so much a lib lib ?
If we do that, then all other places where the ass
On Tue, May 24, 2011 at 2:50 AM, Hans Verkuil wrote:
> On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
>> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
>> during the weekend, I decided to add alsa support also on xawtv3, basically
>> to provide a real
Em 24-05-2011 03:50, Hans Verkuil escreveu:
> On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
>> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
>> during the weekend, I decided to add alsa support also on xawtv3, basically
>> to provide a real usecase ex
Em 24-05-2011 04:21, Hans de Goede escreveu:
> Hi,
> My I suggest that we instead just copy over the single get_media_devices.c
> file to xawtv, and not install the not so much a lib lib ?
If we do that, then all other places where the association between an alsa
device
and a video4linux node i
Hi,
On 05/24/2011 08:50 AM, Hans Verkuil wrote:
On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
during the weekend, I decided to add alsa support also on xawtv3, basically
to provide a real usecase examp
On Monday, May 23, 2011 22:17:06 Mauro Carvalho Chehab wrote:
> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
> during the weekend, I decided to add alsa support also on xawtv3, basically
> to provide a real usecase example. Of course, for it to work, it needs the
>
Em 23-05-2011 17:19, Devin Heitmueller escreveu:
> On Mon, May 23, 2011 at 4:17 PM, Mauro Carvalho Chehab
> wrote:
>> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
>> during the weekend, I decided to add alsa support also on xawtv3, basically
>> to provide a real us
Em 23-05-2011 17:19, Devin Heitmueller escreveu:
> On Mon, May 23, 2011 at 4:17 PM, Mauro Carvalho Chehab
> wrote:
>> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
>> during the weekend, I decided to add alsa support also on xawtv3, basically
>> to provide a real us
On Mon, May 23, 2011 at 4:17 PM, Mauro Carvalho Chehab
wrote:
> Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
> during the weekend, I decided to add alsa support also on xawtv3, basically
> to provide a real usecase example. Of course, for it to work, it needs the
>
Due to the alsa detection code that I've added at libv4l2util (at v4l2-utils)
during the weekend, I decided to add alsa support also on xawtv3, basically
to provide a real usecase example. Of course, for it to work, it needs the
very latest v4l2-utils version from the git tree.
I've basically adde
41 matches
Mail list logo
