Em 19-03-2012 19:05, Ezequiel García escreveu:
> Hi Mauro,
>
> On 3/7/12, Mauro Carvalho Chehab wrote:
>>
>> The usage of saa711x is simple. All you need to do is to implement
>> an I2C bus at your easycap driver, load the module, and then, redirect
>> any demod ioctl call to the I2C bus, like:
>
Hi Mauro,
On 3/7/12, Mauro Carvalho Chehab wrote:
>
> The usage of saa711x is simple. All you need to do is to implement
> an I2C bus at your easycap driver, load the module, and then, redirect
> any demod ioctl call to the I2C bus, like:
>
> static int vidioc_querystd(struct file *file, void *pr
Em 07-03-2012 17:39, Ezequiel García escreveu:
> Hi Mauro,
>
>>
>> em28xx is a good reference.
>>
>
> I'm looking at it.
> In fact, I have a first question: why there is a limit to the number of
> devices
> the driver support? I found the same idea in easycap original
> implementation, but I
> c
Hi Mauro,
>
> em28xx is a good reference.
>
I'm looking at it.
In fact, I have a first question: why there is a limit to the number of devices
the driver support? I found the same idea in easycap original
implementation, but I
can't understand why do we have to limit in such a way.
/* Ch
Em 07-03-2012 13:45, Ezequiel García escreveu:
> On Wed, Mar 7, 2012 at 1:35 PM, Mauro Carvalho Chehab
> wrote:
>>
>> Yes, the driver is weird, as it encapsulates the demod code
>> inside it , instead of using the saa7115 driver, that covers most
>> of saa711x devices, including saa7113.
>>
>> Btw
On Wed, Mar 7, 2012 at 1:35 PM, Mauro Carvalho Chehab
wrote:
>
> Yes, the driver is weird, as it encapsulates the demod code
> inside it , instead of using the saa7115 driver, that covers most
> of saa711x devices, including saa7113.
>
> Btw, is this driver really needed? The em28xx driver has sup
Em 07-03-2012 12:43, gregkh escreveu:
> On Wed, Mar 07, 2012 at 11:32:23AM -0300, Ezequiel García wrote:
>> Hi,
>>
>>>
>>> Have you considered instead slowly moving the existing easycap driver
>>> over to all the new infrastructure we have now. For starters replace
>>> its buffer management with vi
On Wed, Mar 07, 2012 at 11:32:23AM -0300, Ezequiel García wrote:
> Hi,
>
> >
> > Have you considered instead slowly moving the existing easycap driver
> > over to all the new infrastructure we have now. For starters replace
> > its buffer management with videobuf2, then in another patch replace
>
Hi,
>
> Have you considered instead slowly moving the existing easycap driver
> over to all the new infrastructure we have now. For starters replace
> its buffer management with videobuf2, then in another patch replace
> some other bits, etc. ? See what I've done to the pwc driver :)
Yes. And th
Hi,
On 03/06/2012 10:04 PM, Ezequiel García wrote:
Hello,
After some research on v4l2 and videbuf2, and considering that easycap
driver is pretty
outdated I've decided to start writing a new driver from scratch.
I am using the excellent vivi driver and some usb video capture drivers as
a start
Hello,
After some research on v4l2 and videbuf2, and considering that easycap
driver is pretty
outdated I've decided to start writing a new driver from scratch.
I am using the excellent vivi driver and some usb video capture drivers as
a starting point. And of course, I'm using the current easyca
Hello,
After some research on v4l2 and videbuf2, and considering that easycap
driver is pretty
outdated I've decided to start writing a new driver from scratch.
I am using the excellent vivi driver and some usb video capture drivers as
a starting point. And of course, I'm using the current easyca
12 matches
Mail list logo
