From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: gregkh <gregkh@linuxfoundation.org>
Cc: "Ezequiel García" <elezegarcia@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Tomas Winkler" <tomasw@gmail.com>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: A second easycap driver implementation
Date: Wed, 07 Mar 2012 13:35:49 -0300 [thread overview]
Message-ID: <4F578E65.4070409@redhat.com> (raw)
In-Reply-To: <20120307154311.GB14836@kroah.com>
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 videobuf2, then in another patch replace
>>> some other bits, etc. ? See what I've done to the pwc driver :)
>>
>> Yes. And that was what I was doing until now.
>> Yet, after some work it seemed much easier
>> to simply start over from scratch.
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 support
for the Easy Cap Capture DC-60 model (I had access to one of those
in the past, and I know that the driver works properly).
What's the chipset using on your Easycap device?
If it is not an Empiatech em28xx USB bridge, then it makes sense
to have a separate driver for it. Otherwise, it is just easier
and better to add support for your device there.
>>
>> Besides, it's being a great learning experience :)
>>
>> So, since the driver is not yet working I guess there
>> is no point in submitting anything.
>>
>> Instead, anyone the wants to help I can send what I have now
>> or we can start working through github.
>> If someone owns this device, it would be a *huge* help
>> with testing.
>>
>> However, as soon as this is capturing video I would like
>> to put it on staging, so everyone can help.
>> Is this possible?
>
> Yes it is, just send the patches to the correct people (note I don't
> control the drivers/staging/media subdirectory.)
>
> good luck,
>
> greg k-h
next prev parent reply other threads:[~2012-03-07 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 21:04 A second easycap driver implementation Ezequiel García
2012-03-06 21:05 ` Ezequiel García
2012-03-07 9:10 ` Hans de Goede
2012-03-07 14:32 ` Ezequiel García
2012-03-07 15:43 ` gregkh
2012-03-07 16:35 ` Mauro Carvalho Chehab [this message]
2012-03-07 16:45 ` Ezequiel García
2012-03-07 17:17 ` Mauro Carvalho Chehab
2012-03-07 20:39 ` Ezequiel García
2012-03-07 20:53 ` Mauro Carvalho Chehab
2012-03-19 22:05 ` Ezequiel García
2012-03-19 22:34 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F578E65.4070409@redhat.com \
--to=mchehab@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=elezegarcia@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=tomasw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.