From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Wed, 19 Apr 2006 11:57:42 +0000 Subject: Re: udevtest conflicts with reality Message-Id: <20060419115742.GB26172@vrfy.org> 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 On Tue, Apr 18, 2006 at 05:32:14PM -0500, Brent Casavant wrote: > 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. > UDEV [1145397289.791917] add@/class/extint/extint0 > UDEV_LOG=3D7 > ACTION=ADd > DEVPATH=3D/class/extint/extint0 > SUBSYSTEM=3Dextint > SEQNUM=1427 > UDEVD_EVENT=3D1 Looks like the driver is not using the driver core properly and you don't pass the dev_t to the class function, which will automatically create the "dev" file in sysfs and add MAJOR=3D, MINOR=3D to the event environment. Recent udev versions depend on the variable in the environment and don't open the "dev" file like udevtest is doing it. Kay ------------------------------------------------------- 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