Bug 3527 - Support for v4l hardware
Summary: Support for v4l hardware
Alias: None
Product: hal
Classification: Unclassified
Component: hald (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: David Zeuthen (not reading bugmail)
QA Contact:
Depends on:
Reported: 2005-06-12 15:10 UTC by Nickolay V. Shmyrev
Modified: 2006-08-07 01:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Note You need to log in before you can comment on or make changes to this bug.
Description Nickolay V. Shmyrev 2005-06-12 15:10:43 UTC

As I know, hal 0.4 had support for v4l hardware, now I see it's disappeared in
0.5. Can you point me to things that I should do to return it back.
Comment 1 Tobias 2005-10-15 01:47:43 UTC
I was just looking for a similar thing and found this (Perhapy it helps):

2004-09-13  Kay Sievers  <kay.sievers@vrfy.org>

	* hald/linux/multimedia_class_device.c:
	(multimedia_class_device_accept), (multimedia_class_pre_process):
	New file for initial support of video4linux devices. It's just
	a starting point and we need more input from users of v4l
	devices. For a simple webcam it currently looks like this:
	   multimedia.device = '/udev/video0'  (string)
	   info.category = 'multimedia'  (string)
	   multimedia.video.can_capture = true  (bool)
	   multimedia.audio.has_audio = false  (bool)
	   multimedia.tuner.has_tuner = false  (bool)
	   multimedia.linux.version = 'v4l'  (string)
	   info.udi =
'/org/freedesktop/Hal/devices/usb_device_5a9_a511_100_-1_noserial'  (string)

	* hald/linux/osspec.c:  Add the new multimedia_class_handler to
	probe for video device properties on device discovery

	* tools/device-manager/Representation.py: Change "video" to
	"multimedia" to have a nice icon for the screenshots :)
Comment 2 David Zeuthen (not reading bugmail) 2006-08-02 17:18:10 UTC
(bug triaging) Yes, this should be back on HEAD again.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.