From: Albert Veli <Albert.Veli@afconsult.com>
To: linux-hotplug@vger.kernel.org
Subject: Udev + /dev/rtf
Date: Fri, 03 Mar 2006 13:20:19 +0000 [thread overview]
Message-ID: <1141392019.7276.8.camel@localhost.localdomain> (raw)
Hi,
I have a question about udev and /dev/rtf* device nodes. They are needed
to interact with the module rtai_fifos.ko (part of RTAI, a Linux
realtime extension).
But I'm not sure if rtai_fifos.ko support sysfs or not.
/sys/module/rtai_fifos/ gets created when I load the module but there is
not much in it.
The output of 'udevinfo -a -p /sys/module/rtai_fifos/' is just:
looking at class device '/sys/module/rtai_fifos':
SUBSYSTEM="unknown"
SYSFS{refcnt}="0"
When this module gets loaded, it would be ideal if the device
nodes /dev/rtf[0-9] could be created.
crw-rw-rw- 1 root root 150, 0 2006-03-03 14:05 /dev/rtf0
crw-rw-rw- 1 root root 150, 1 2006-03-03 14:05 /dev/rtf1
...
crw-rw-rw- 1 root root 150, 9 2006-03-03 14:05 /dev/rtf9
If I create the device nodes manually with mknod they get erased when
the box is rebooted.
Does anobody know if it is possible to make these device nodes
persistent with udev somehow?
(or even better, created when the module is loaded and deleted when the
module is unloaded)
If it is possible, how should a /etc/udev/rules.d rules file look like?
I tried with:
DRIVER="rtai_fifos", NAME="rtf%n"
But nothing happened..
Regards, Albert
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&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 reply other threads:[~2006-03-03 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 13:20 Albert Veli [this message]
2006-03-03 13:24 ` Udev + /dev/rtf Marco d'Itri
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=1141392019.7276.8.camel@localhost.localdomain \
--to=albert.veli@afconsult.com \
--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).