From: Hans de Goede <hdegoede@redhat.com>
To: Erik de Castro Lopo <erik@bcode.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: GPL code for Omnivision USB video camera available.
Date: Mon, 15 Jun 2009 23:00:04 +0200 [thread overview]
Message-ID: <4A36B654.7020306@redhat.com> (raw)
In-Reply-To: <20090615110152.4c577be7.erik@bcode.com>
On 06/15/2009 03:01 AM, Erik de Castro Lopo wrote:
> On Sat, 13 Jun 2009 18:12:10 +1000
> Hans de Goede<hdegoede@redhat.com> wrote:
>
>> Getting ovfx2 support into the mainline kernel sounds like a good idea!
>>
>> I'm not such a big fan of merging the driver as is though, as it does
>> its own buffer management (and ioctl handling, usb interrupt handling,
>> locking, etc).
>
> I understand completely.
>
Good!
>> For adding the ovfx2 driver, you could start by copying ov519.c, which
>> already has setup and control code fro most ov sensors and then rewrite
>> the bridge part to be ovfx2 code, then later we can try to move the
>> sensor code to a shared c file for the ov519 and ovfx2 driver, depending
>> on how much you needed to change the sensor code. Or you could add
>> support for the ovfx2 to the ov519 driver.
>>
>> Note I've recently being doing quite a bit of work on the ov519 driver,
>> adding support for the ov511 and ov518 and adding more controls. I'll
>> make a mercurial tree available with my latest code in it asap.
>
> Ok, there's the rub. I am simply way too busy at the moment to push this
> through myself.
>
> I was hoping I could contract someone to take the existing code and
> massage it into shape ready for merging. I would prefer it if that
> someone was already a V4L hacker, but if I can't find anyone with
> pre-existing V4L experience I'll find someone local with general
> Linux kernel/driver experience.
>
Well I can't offer you contracting, as I simply do not have the spare time
to make such promises, but as any good hacker: "will work for hardware"
on a I'll do my best but no promises made basis.
I'm actually spending quite a bit of time lately on v4l stuff again,
and I'm sure willing to spend some time on this. I can even promise you
I'll bump it to the top of the list of my v4l projects.
For a general idea how deep I'm involved in v4l webcam support see:
https://fedoraproject.org/wiki/Features/BetterWebcamSupport
Regards,
Hans
next prev parent reply other threads:[~2009-06-15 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 1:02 GPL code for Omnivision USB video camera available Erik de Castro Lopo
2009-06-12 6:51 ` Hans de Goede
2009-06-13 0:45 ` Erik de Castro Lopo
2009-06-13 8:12 ` Hans de Goede
2009-06-15 1:01 ` Erik de Castro Lopo
2009-06-15 21:00 ` Hans de Goede [this message]
2009-06-14 9:51 ` Hans de Goede
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=4A36B654.7020306@redhat.com \
--to=hdegoede@redhat.com \
--cc=erik@bcode.com \
--cc=linux-media@vger.kernel.org \
/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.