From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrey Borzenkov Date: Wed, 19 Apr 2006 03:00:58 +0000 Subject: Re: udevtest conflicts with reality Message-Id: <200604190701.07793.arvidjaar@mail.ru> List-Id: References: <20060418171520.J25073@chenjesu.americas.sgi.com> In-Reply-To: <20060418171520.J25073@chenjesu.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org -----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 =3D '253', minor = > '0', mode =3D '0660', uid =3D '0', gid =3D '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=3D"/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 > ACTION=ADd > DEVPATH=3D/class/extint/extint0 > SUBSYSTEM=3Dextint > SEQNUM=1427 > 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=3DYb9V -----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=3Dlnk&kid=110944&bid$1720&dat=121642 _______________________________________________ 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