From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: video4linux-list@redhat.com
Subject: Re: weeding out v4l ver 1 stuff
Date: Fri, 07 Nov 2008 08:10:19 +0100 [thread overview]
Message-ID: <4913E9DB.8040801@hhs.nl> (raw)
In-Reply-To: <30353c3d0811061553h4c1a77e0t597bd394fa0ebdf1@mail.gmail.com>
David Ellingsworth wrote:
> On Thu, Nov 6, 2008 at 1:39 PM, Carl Karsten <carl@personnelware.com> wrote:
>> Given v4l version 1 is being dropped in December 08, we should remove stuff that
>> targets that api, right?
>>
>> For instance:
>>
>> http://linuxtv.org/hg/v4l-dvb/file/b45ffc93fb82/v4l2-apps/test/v4lgrab.c
>>
>> 94 #ifdef CONFIG_VIDEO_V4L1_COMPAT
>> 194 #else
>>
>> 195 fprintf(stderr, "V4L1 API is not configured!\n");
>>
>> I'll let someone else figure out if the whole file should be removed, or if it
>> has some value to v2.
>>
>> And assuming someone agrees we should week out v1 stuff, where is the right
>> place to log this too? http://bugzilla.kernel.org does not seem right.
>>
>> Carl K
>>
>
> With v4l1 going away, it would be nice to convert any drivers still
> using the v4l1 interface to v4l2. Drivers using usbvideo spring to
> mind. I've mentioned in the past, I've started a rewrite of ibmcam
> over to the v4l2 interface but I currently don't have much time to
> work on it and could use some assistance from the community. While
> Mauro suggested it be written against the gspca framework, I hesitate
> to do so since gspca does it's own memory management and will probably
> become somewhat obsolete once the new media framework is put together.
? What new media framework ? You mean the planned changes to the v4l2 API for
multifunction devices? Anyways this won't make gspca obsolete, gspca is a
framework for writing usb webcam drivers, as such it tries to do things common
to all usb webcam drivers inside the gspca-core. If the v4l2 core changes the
gspca-core will adapt and in most cases of v4l2-core changes, the gspca
subdrivers will not need to change at all. So if anything using gspca makes
your driver more future proof against v4l2-core changes as in most cases the
necessary changes for all gspca drivers only need to be made once in gspca-core
Regards,
Hans
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-07 7:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 18:39 weeding out v4l ver 1 stuff Carl Karsten
2008-11-06 23:53 ` David Ellingsworth
2008-11-07 7:10 ` Hans de Goede [this message]
2008-11-07 9:50 ` Hans Verkuil
2008-11-07 15:19 ` Antonio Ospite
2008-11-07 19:26 ` USB Capture device Keith Lawson
2008-11-13 11:57 ` Keith Lawson
2008-11-13 12:40 ` Markus Rechberger
2008-11-14 15:37 ` Keith Lawson
2008-11-14 15:50 ` Markus Rechberger
2008-11-14 15:55 ` RE : " Jonathan Lafontaine
2008-11-14 16:45 ` Jonathan Lafontaine
2008-11-14 19:44 ` MODRPOBE RMMOD Jonathan Lafontaine
2008-11-14 23:29 ` Ben Klein
[not found] ` <d7e40be30811141517p5700f803t731ec578f1cabd59@mail.gmail.com>
2008-11-14 23:18 ` USB Capture device Ben Klein
2008-11-15 2:11 ` hermann pitton
2008-11-15 15:18 ` Keith Lawson
2008-11-15 4:56 ` Markus Rechberger
2008-11-07 20:43 ` weeding out v4l ver 1 stuff Mauro Carvalho Chehab
2008-11-07 20:45 ` 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=4913E9DB.8040801@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=david@identd.dyndns.org \
--cc=video4linux-list@redhat.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.