From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevtest conflicts with reality
Date: Wed, 19 Apr 2006 03:00:58 +0000 [thread overview]
Message-ID: <200604190701.07793.arvidjaar@mail.ru> (raw)
In-Reply-To: <20060418171520.J25073@chenjesu.americas.sgi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 19 April 2006 02:32, Brent Casavant wrote:
> Hello,
>
> I'm attempting to get the /dev/extint0 device, corresponding to SGI's
> external interrupt driver to be created. (FWIW: This driver was
> open-sourced, and submitted to lkml, but never accepted. SGI just
> ships it and its source as part of its system software). This is
> with a 2.6.16 kernel, and udev-085.
>
> When using the default rules, udevtest indicates things "should work",
> as follows:
>
> --- cut here ---
> # udevtest /class/extint/extint0
> main: looking at device '/class/extint/extint0' from subsystem 'extint'
> udev_rules_get_name: no node name set, will use kernel name 'extint0'
> create_node: creating device node '/dev/extint0', major = '253', minor > '0', mode = '0660', uid = '0', gid = '0' main: run:
> 'socket:/org/freedesktop/hal/udev_event'
> main: run: 'socket:/org/kernel/udev/monitor'
> --- cut here ---
>
> However the /dev/extint0 node is not created when the module is loaded.
>
> I've tried my own rules files and such, which seem to kick in as expected,
> but still no nodes are created. Using a RUN="/bin/mknod /dev/foo c %M %m"
> worked in that it ran, however the major and minor number came out as
> zeroes.
>
which means device number is not defined.
> udevmonitor --env yielded the following:
[...]
>
> UEVENT[1145397289.786662] add@/class/extint/extint0
> ACTIONd
> DEVPATH=/class/extint/extint0
> SUBSYSTEM=extint
> SEQNUM\x1427
>
No device here either
[...]
>
> ioc4_extint is suffering the same problem, and it should be noted that
> the load of ioc4_extint triggers the creation of the extint device
> (i.e. extint provides an abstracted interface to the lower-level
> ioc4_extint device).
>
> Any hints on where to go from here?
>
Does /sys/class/extint/extint0/dev exists and what does it contain?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFERafzR6LMutpd94wRAohLAJ9BpIJTiurTXaJK+r3iqalZ91csSgCfWLs+
eeudx0RK8sbR2zXAqn0/mQ8=Yb9V
-----END PGP SIGNATURE-----
-------------------------------------------------------
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 prev parent reply other threads:[~2006-04-19 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 22:32 udevtest conflicts with reality Brent Casavant
2006-04-19 3:00 ` Andrey Borzenkov [this message]
2006-04-19 11:57 ` Kay Sievers
2006-04-19 15:36 ` Brent Casavant
2006-04-19 21:04 ` Greg KH
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=200604190701.07793.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).