From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevtest conflicts with reality
Date: Wed, 19 Apr 2006 11:57:42 +0000 [thread overview]
Message-ID: <20060419115742.GB26172@vrfy.org> (raw)
In-Reply-To: <20060418171520.J25073@chenjesu.americas.sgi.com>
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=7
> ACTIONd
> DEVPATH=/class/extint/extint0
> SUBSYSTEM=extint
> SEQNUM\x1427
> UDEVD_EVENT=1
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=, MINOR= 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=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 11:57 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
2006-04-19 11:57 ` Kay Sievers [this message]
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=20060419115742.GB26172@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).