All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	David Ellingsworth <david@identd.dyndns.org>
Subject: Re: RFC: Phase 1: Proposal to convert V4L1 drivers
Date: Tue, 23 Mar 2010 12:04:07 +0100	[thread overview]
Message-ID: <4BA8A027.90702@redhat.com> (raw)
In-Reply-To: <201003221155.45733.hverkuil@xs4all.nl>

Hi,

On 03/22/2010 11:55 AM, Hans Verkuil wrote:
> On Monday 22 March 2010 10:29:09 Hans de Goede wrote:
>> Hi,
>>
>> On 03/22/2010 01:17 AM, Hans Verkuil wrote:
>>> On Sunday 21 March 2010 23:45:04 Hans Verkuil wrote:
>>>> On Saturday 20 March 2010 09:58:49 Hans Verkuil wrote:
>>>>> These drivers have no hardware to test with: bw-qcam, c-qcam, arv, w9966.
>>>>> However, all four should be easy to convert to v4l2, even without hardware.
>>>>> Volunteers?
>>>>
>>>> I've converted these four drivers to V4L2.
>>>
>>> I've also removed the V4L1 support from cpia2 and pwc and removed some last
>>> V4L1 code remnants from meye and zoran. It's all in the same tree.
>>>
>>> Hans, could you test the pwc driver for me?
>>>
>>
>> Done,
>>
>> And the news is not good I'm afraid, it does not work. I've one interesting
>> observation though. It does work if I first run it once with the "old"
>> version of the driver and then load your version (also replacing videodev.ko,
>> etc with the ones from your tree). But if I plug it in with your driver in
>> place it does not stream (nothing interesting in dmesg). So it seems like
>> an initialization problem.
>
> When you run it with the old version, are you using the V4L1 API or the V4L2
> API? And what program do you use for testing?
>

I was using cheese, which uses the V4l2 api (through gstreamer).

Regards,

Hans

  reply	other threads:[~2010-03-23 11:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  8:58 RFC: Phase 1: Proposal to convert V4L1 drivers Hans Verkuil
2010-03-20 18:38 ` Gerard Klaver
2010-03-21 16:40   ` Hans Verkuil
2010-03-20 18:42 ` Devin Heitmueller
2010-03-20 21:53 ` Hans Verkuil
2010-03-20 23:12   ` Hans de Goede
2010-03-20 23:09 ` Hans de Goede
2010-03-21  8:19   ` Hans Verkuil
2010-03-21  9:13     ` Nicolas Will
2010-03-21 22:45 ` Hans Verkuil
2010-03-22  0:17   ` Hans Verkuil
2010-03-22  9:29     ` Hans de Goede
2010-03-22 10:55       ` Hans Verkuil
2010-03-23 11:04         ` Hans de Goede [this message]
2010-03-22 14:37       ` Theodore Kilgore

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=4BA8A027.90702@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=david@identd.dyndns.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --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.