After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 131320 - v4l & v4l2 : bad auto-detection
v4l & v4l2 : bad auto-detection
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-13 10:41 UTC by Stephane Loeuillet
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Attachments
my linux/videodev.h which handles both v4l & v4l2 (14.13 KB, text/plain)
2004-01-13 10:43 UTC, Stephane Loeuillet
Details

Description Stephane Loeuillet 2004-01-13 10:41:52 UTC
i have a v4l2 (yep, v2) bttv driver under kernel 2.4.24.

in gst-plugins, v4l is compiled when linux/videodev.h is found and v4l2 is
compiled when linux/videodev2.h is found.

perhaps it works for kernel 2.6.x (i don't have one to test it) but it
won't work on 2.4.x as a single linux/videodev.h is used for both v4l and v4l2.

--

the second thing i can see is that video device in the v4lX plug-ins is
called /dev/video or /dev/v4l/video

the problem is that it sometimes is called /dev/video0 (symlink to
/dev/v4l/video0)

so, it is configurable somewhere when i say that videosrc is v4lXsrc ?
Comment 1 Stephane Loeuillet 2004-01-13 10:43:29 UTC
Created attachment 23301 [details]
my linux/videodev.h  which handles both v4l & v4l2
Comment 2 Stephane Loeuillet 2004-01-13 10:55:57 UTC
argh, part 1 of this bug is invalid
got a videodev2.h in my /usr/src/linux-2.4.24 but was not in
/usr/include/linux

----

the problem/question for video device naming is still open
Comment 3 Ronald Bultje 2004-01-13 12:34:34 UTC
It's a property (see gst-inspect v4lsrc or gst-inspect v4l2src).
gst-launch v4lsrc device=/dev/video0 ! ffcolorspace ! ximagesink
should give an image.

(Marking as fixed since the question should be answered now... Feel
free to re-open...)