From: Jim Gifford <maillist@jg555.com>
To: linux-hotplug@vger.kernel.org
Subject: Udev - Hot/Cold Plugging and Sparc
Date: Fri, 20 Jan 2006 00:47:28 +0000 [thread overview]
Message-ID: <43D03320.6050301@jg555.com> (raw)
First of thank you Kay and Greg, with all the information you have
provided, I was able to make a usable udev package. Now I'm working on
getting the same package to recognize some exotic hardware and hope you
guys can provide some guidance.
On the x86, the rtc module gets located ok and loads, while on the sparc
it doesn't seem to ever find it, not sure if it's a script problem, udev
problem, or it's a module issue. I do know when I modprobe rtc, it shows
up, but when I run udevinfo, I don't see enough useful information to
create a rule. Output below.
udevinfo -a -p /sys/class/misc/rtc
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at device '/class/misc/rtc':
KERNEL="rtc"
SUBSYSTEM="misc"
SYSFS{dev}="10:135"
--
----
Jim Gifford
maillist@jg555.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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-01-20 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 0:47 Jim Gifford [this message]
2006-01-20 0:55 ` Udev - Hot/Cold Plugging and Sparc Marco d'Itri
2006-01-20 3:46 ` Andrey Borzenkov
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=43D03320.6050301@jg555.com \
--to=maillist@jg555.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).