From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: issues getting I/O device to work with udev....
Date: Fri, 25 Aug 2006 12:59:43 +0000 [thread overview]
Message-ID: <1156510783.3597.159.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <20060823222620.GA1164@seberino.org>
On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > fact that the device gets created under /dev/edredaq/device0-99. This
> > rules
> > > worked just fine on previous systems, but suddenly it started to fail on
> > > newer distros.
> > > Can you guys maybe point me to a solution?
> >
> > Hmm, what exactly is the problem? What suddenly started to fail?
> > Can you paste the output of 'udevmonitor' when you load the kernel
> > module? Or the output when connect the USB device, if you only have it
> > built-in.
> The node /dev/edredaq/device0 never get created, or it does not show up in
> the file system (maybe it's permission / security related). Unfortunately I
> have left work already and cannot do the 'udevmonitor' for you.
Oh, that all sounds very much like you don't use the right driver core
functions and you create the "dev" file yourself in sysfs. You must use
the right functions in the kernel and pass the correct dev_t to the
device registration. That will automatically create the "dev" file and
add the needed data to the uevent environment, to let udev create the
node.
But again, to verify this, we need the output of "udevmonitor --env",
while you plug in a device or re-trigger the event by writing "add" to
the "uevent" file in the sysfs device directory.
Kay
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-08-25 12:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 22:26 issues getting I/O device to work with udev chris
2006-08-23 22:34 ` Marco d'Itri
2006-08-23 23:02 ` chris
2006-08-23 23:10 ` Kay Sievers
2006-08-23 23:14 ` chris
2006-08-23 23:18 ` Kay Sievers
2006-08-23 23:47 ` chris
2006-08-25 9:19 ` Jan Zwiegers
2006-08-25 10:36 ` Kay Sievers
2006-08-25 11:38 ` Jan Zwiegers
2006-08-25 11:41 ` Jan Zwiegers
2006-08-25 12:59 ` Kay Sievers [this message]
2006-08-25 13:47 ` Jan Zwiegers
2006-08-25 14:02 ` Kay Sievers
2006-08-25 19:22 ` Jan Zwiegers
2006-08-26 4:48 ` Greg KH
2006-08-26 6:04 ` Jan Zwiegers
2006-08-26 18:08 ` Greg KH
2006-08-26 19:33 ` Jan Zwiegers
2006-08-27 0:18 ` Kay Sievers
2006-08-30 13:52 ` Jan Zwiegers
2006-08-30 17:51 ` Greg KH
2006-08-31 11:44 ` Jan Zwiegers
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=1156510783.3597.159.camel@pim.off.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).