From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-media@vger.kernel.org
Subject: Re: Removal of V4L1 drivers
Date: Sat, 25 Dec 2010 07:07:51 -0200 [thread overview]
Message-ID: <4D15B467.90004@redhat.com> (raw)
In-Reply-To: <201012241442.39702.hverkuil@xs4all.nl>
Em 24-12-2010 11:42, Hans Verkuil escreveu:
> Hi Hans, Mauro,
>
> The se401, vicam, ibmcam and konicawc drivers are the only V4L1 drivers left in
> 2.6.37. The others are either converted or moved to staging (stradis and cpia),
> ready to be removed.
>
> Hans, what is the status of those four drivers? How likely is it that they will be
> converted to V4L2?
>
> If we can't convert them to V4L2 for 2.6.38, then we can at least remove the
> V4L1_COMPAT code throughout the v4l drivers and move those four drivers to staging.
>
> For 2.6.39 we either remove them or when they are converted to V4L2 they are moved
> out of staging again (probably to gspca).
>
> As an illustration I have removed the V4L1_COMPAT mode in this branch:
>
> http://git.linuxtv.org/hverkuil/media_tree.git?a=shortlog;h=refs/heads/v4l1
Seems ok for me.
>
> There are two drivers that need more work: stk-webcam has some controls under sysfs
> that are enabled when CONFIG_VIDEO_V4L1_COMPAT is set. These controls should be
> rewritten as V4L2 controls. Hans, didn't you have hardware to test this driver?
> I should be able to make a patch that you can test.
The conversion seems trivial. Even knowing that none of us have that hardware, I think
we should just convert it and apply the patch. We'll have the entire .38 kernel cycle for
people to test.
> The other driver is the zoran driver which has a bunch of zoran-specific ioctls
> under CONFIG_VIDEO_V4L1_COMPAT. I think I can just delete the lot since they are
> all replaced by V4L2 counterparts AFAIK. But it would be good if someone else can
> also take a look at that.
They seem to mimic v4l2. Also, they implement their own private API, and this is a bad
thing. I doubt that most applications would use that API. So, if the driver works fine
with just V4L2, I think it is ok to just remove that old code. So let's go ahead and
remove, asking people to test it. I'll do some tests also in Jan.
Cheers,
Mauro
prev parent reply other threads:[~2010-12-25 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 13:42 Removal of V4L1 drivers Hans Verkuil
2010-12-24 14:47 ` Hans de Goede
2010-12-24 18:58 ` Hans Verkuil
2010-12-24 19:55 ` Hans de Goede
2010-12-25 9:18 ` Mauro Carvalho Chehab
2010-12-25 9:40 ` Hans Verkuil
2010-12-25 9:11 ` Mauro Carvalho Chehab
2010-12-25 9:07 ` Mauro Carvalho Chehab [this message]
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=4D15B467.90004@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox