From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: PATCH: Priority=high: luca-drivers-parent-fix.patch
Date: Mon, 01 Sep 2008 20:28:23 +0200 [thread overview]
Message-ID: <48BC3447.1060804@hhs.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Hi Mauro,
I didn't know through which tree to send this as Luca's drivers are
unmaintained so I'm sending this directly to you. I would like to see this make
2.6.27 as without this any cams using Luca's drivers do not work out of the box
(they require a manual chmod to allow non root access after plugging them in).
###
While doing some testing using Luca Risolia's sonix driver I noticed that
the video device did not get ACL's set to allow access by locally logged in
users, nor does it show up as a video device in lshal, causing cheese to not
see it.
This turns out to be caused by all of Luca Risolia's drivers not setting
the parent member of the video_device struct. This patch fixes this.
Priority: high
Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
Regards,
Hans
[-- Attachment #2: luca-drivers-parent-fix.patch --]
[-- Type: text/plain, Size: 1904 bytes --]
While doing some testing using Luca Risolia's sonix driver I noticed that
the video device did not get ACL's set to allow access by locally logged in
users, nor does it show up as a video device in lshal, causing cheese to not
see it.
This turns out to be caused by all of Luca Risolia's drivers not setting
the parent member of the video_device struct. This patch fixes this.
Priority: high
Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
diff -r 01f8914508b4 linux/drivers/media/video/et61x251/et61x251_core.c
--- a/linux/drivers/media/video/et61x251/et61x251_core.c Sun Aug 31 19:25:43 2008 +0200
+++ b/linux/drivers/media/video/et61x251/et61x251_core.c Mon Sep 01 20:20:14 2008 +0200
@@ -2592,6 +2592,7 @@
cam->v4ldev->fops = &et61x251_fops;
cam->v4ldev->minor = video_nr[dev_nr];
cam->v4ldev->release = video_device_release;
+ cam->v4ldev->parent = &udev->dev;
video_set_drvdata(cam->v4ldev, cam);
init_completion(&cam->probe);
diff -r 01f8914508b4 linux/drivers/media/video/sn9c102/sn9c102_core.c
--- a/linux/drivers/media/video/sn9c102/sn9c102_core.c Sun Aug 31 19:25:43 2008 +0200
+++ b/linux/drivers/media/video/sn9c102/sn9c102_core.c Mon Sep 01 20:20:14 2008 +0200
@@ -3316,6 +3316,7 @@
cam->v4ldev->fops = &sn9c102_fops;
cam->v4ldev->minor = video_nr[dev_nr];
cam->v4ldev->release = video_device_release;
+ cam->v4ldev->parent = &udev->dev;
init_completion(&cam->probe);
diff -r 01f8914508b4 linux/drivers/media/video/zc0301/zc0301_core.c
--- a/linux/drivers/media/video/zc0301/zc0301_core.c Sun Aug 31 19:25:43 2008 +0200
+++ b/linux/drivers/media/video/zc0301/zc0301_core.c Mon Sep 01 20:20:14 2008 +0200
@@ -1992,6 +1992,7 @@
cam->v4ldev->fops = &zc0301_fops;
cam->v4ldev->minor = video_nr[dev_nr];
cam->v4ldev->release = video_device_release;
+ cam->v4ldev->parent = &udev->dev;
video_set_drvdata(cam->v4ldev, cam);
init_completion(&cam->probe);
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
reply other threads:[~2008-09-01 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48BC3447.1060804@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox