Red Hat Bugzilla – Bug 209112
Review Request: gspca - v4l2 kernel module driver for webcams
Last modified: 2007-11-30 17:11:45 EST
Spec URL: http://people.redhat.com/pnemade/gspca/gspca-kmod.spec
SRPM URL: http://people.redhat.com/pnemade/gspca/gspca-kmod-20060930-220.127.116.11_1.2708.fc6.src.rpm
Description: This is kernel module written using v4l2 APIs for webcams.
I got information from gspca author
Why Module is not in mainstream kernel and when it will be in kernel?
==>From the first times we have to deal with jpeg hardware, video jpeg (raw
jpeg) is not human readable. For some reason kernel people, did not want to play
with video decoding in the kernel. That is why, spca50x, spca5xx and now gspca
is outside the kernel tree. Now somethings have changed(with change of userspace
applications need to understand what a video compressor is) with v4l2, we can
forward the raw video to userspace, so maybe one day gspca will go in
what you think about this information? Is this sufficient or need more? Its
clear now that gspca will be coming in future releases of upstream kernel.
Reply out of order:
(In reply to comment #1)
> Its clear now that gspca will be coming in future releases of upstream kernel.
Well, "so maybe one day will go in the kernel" doesn't sound as if there are
actual plans to work on the integration. A more clear statement would be much
> what you think about this information? Is this sufficient or need more?
I can forward it to FESCo and we can discuss it. I suppose it's enough to get
some people rise their hands for "we allow this module in Extras". But there
will also be some people that won't like this. I already know one particular
member that will say "this is not enough, I don't want this module in extras".
I poked around in the tarball for gspca. In the gspcav2 directory, which this
kmod is being built with, there is a file called ReadMe_First. It contains the
For developper only !!
Don't used, Can BURN your Linux Box and maybe loss all your data !!!
Enjoy V4L2 :)
That doesn't give me warm fuzzy feelings. Then there is the
README-KERNEL-UPTO-2.6.16 file in the Doc directory that talks about conflicts
with in-kernel drivers.
So given that:
1) The driver appears to be a development version only
2) There is documentation that talks of conflict with drivers that are already
in the kernel
3) There is no firm commitment from the driver developers to get this module
into the mainline kernel
I'm against including this in Extras.
thl, I request you then to close this bug with whatever resolution you want.
I got very much disappointed that many peoples are happily using this kmod and
still FESCO is not accepting this thing. I agree there is no firm commitment
when kmod will be included in main kernel.
Yes this kmod is development version but users of this kmod are very happy
(including me :) )
This was discussed in the FESCo meeting today. The largest concern is the need
to get kmods in the upstream kernel (all kmods, not just this one). After
further review and a few testimonials from some developers, we have decided to
approve this kmod for the period of one year. We'll revisit this after that and
see what the status is.
Thank you for your submission, and good luck with your packaging!
Thanks very much to FESCO members for approving this. Before proceeding further
on this review i think i should wait for FE-KMOD-APPROVED set on this bug.
what will be the next step ? I hope to see this module in extras asap.
(In reply to comment #6)
> Thanks very much to FESCO members for approving this. Before proceeding further
> on this review i think i should wait for FE-KMOD-APPROVED set on this bug.
Set. I should have done this earlier. My mistake.
Now i am looking for Sponsor. Is there any FESCO member watching this review can
review this package please?
(In reply to comment #9)
> Now i am looking for Sponsor. Is there any FESCO member watching this review can
> review this package please?
Just to clarify:
- Parag is sponsored already, so all we need is someone that reviews this package
- FESCo members are not needed, just someone with kmod-experiences (scop or I
for example) should do a quick ACK *after* the package was reviewed and aproved
Time to CLOSE this Package Review instead of seeing it as "Awaiting-for-review"
again and again every time Package Status wiki page updated.
I agree its huge work of maintaining kmod packages in Fedora as kernel releases
are very often and kmod packages need to be released for each releases.
After waiting/struggling long here even after getting approval from FESCO,
nobody like to review this package. Though I am sure that many peoples are using
gspca drivers but no one like to see this in Fedora.
Therefore CLOSING this package review.
Thanks to those who commented here and to FESCO for approving this kmod package.
Dunno How to CLOSE this bug (I mean which resolution to use?)
Kindly CLOSE this Review without marking it as DEAD-Review Please.
I think Its CANTFIX.
I don't want this bug to be categorized as DEADREVIEW. I had already commented
Its my wish now I don't want to submit this again besides its gaining more
Removing FE-DEADREVIEW flag, as there is no condition written for reviews which
are in FE-NEW state and submitter is badly needed to see his package in Fedora.