From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bug report: wait_for_sysfs video0
Date: Sat, 16 Oct 2004 16:36:04 +0000 [thread overview]
Message-ID: <20041016163604.GB5031@vrfy.org> (raw)
In-Reply-To: <20041016085957.GB3981@fjellstad.org>
On Sat, Oct 16, 2004 at 01:59:57AM -0700, John L Fjellstad wrote:
> Got the following wait_for_sysfs error message:
> Oct 16 01:52:39 legolas wait_for_sysfs[3934]: either wait_for_sysfs
> (udev 039) needs an update to handle the device
> '/class/video4linux/video0' properly (5) or the sysfs-support of your
> device's driver
>
> content of /sys/class/video4linux/video0:
> john@legolas:~$ ls /sys/class/video4linux/video0/
> dev name
>
> Let me know if you need anything else
This seems like a problem with your device driver. There should be a
symlink to the physical device. Please bug the driver maintainer to
create the "device" and "driver" symlink in the class device, as
hardware/userspace integration depends on proper sysfs use.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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
next prev parent reply other threads:[~2004-10-16 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 8:59 bug report: wait_for_sysfs video0 John L Fjellstad
2004-10-16 16:36 ` Kay Sievers [this message]
2004-10-16 21:30 ` John L Fjellstad
2004-10-16 21:48 ` Kay Sievers
2004-10-16 22:10 ` John L Fjellstad
2004-10-17 0:37 ` Kay Sievers
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=20041016163604.GB5031@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).