From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Trouble managing Trust WebCam
Date: Thu, 18 Nov 2004 17:30:37 +0000 [thread overview]
Message-ID: <1100799037.7238.50.camel@localhost.localdomain> (raw)
In-Reply-To: <1100795386.7474.13.camel@toth>
On Thu, 2004-11-18 at 17:29 +0100, Davide Monge wrote:
> While plugging a "Trust 150 Spacecam portable" into a usb2.0 port, this
> Nov 18 17:10:32 toth wait_for_sysfs[7308]: either wait_for_sysfs (udev
> 044) needs an update to handle the device '/class/video4linux/video0'
> properly (no device symlink) or the sysfs-support of your device's
> driver needs to be fixed, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
The video driver should create a symlink to the physical device, but
that's not the reason your camera is not working.
> Launching Gnomemeeting, all fails in core dumping.
>
> Any idea?
It does not seems like a hotplug problem. You may ask the author of the
driver. If you do that, it would be nice to ask him to link the
class_device to a physical device too.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-11-18 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 16:29 Trouble managing Trust WebCam Davide Monge
2004-11-18 17:30 ` Kay Sievers [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=1100799037.7238.50.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.