From: Terry Barnaby <terry1@beam.ltd.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Question on how to get custom kernel module to work with udev
Date: Fri, 03 Jun 2005 13:33:55 +0000 [thread overview]
Message-ID: <42A05C43.5080707@beam.ltd.uk> (raw)
In-Reply-To: <42A05A1C.80101@beam.ltd.uk>
Terry Barnaby wrote:
> Hi,
>
> I have a custom kernel device driver module for a PCI hardware device
> that I would like
> to integrate with UDEV to get UDEV to generate the /dev nodes.
>
> I am using Fedora Core 3.
> I have not been able to make this work so far, so any ideas ?
>
> When the device is loaded /sbin/hotplug is called with the environment:
>
> export SUBSYSTEM=drivers
> export DEVPATH=/bus/pci/drivers/admxrc2
> export PATH=/sbin:/bin:/usr/sbin:/usr/bin
> export ACTIONd
> export PWD=/
> export SHLVL=1
> export HOME=/
> export SEQNUMx5
> export _=/bin/env
>
> I have added a file /etc/udev/rules.d/40-admxrc.rules with the contents:
>
> KERNEL="admxrc2", NAME="admxrcii%k"
> SYSFS{vendor}="0x4144", NAME="admxrciii%k"
>
> The two line are alternate versions for testing.
>
> I have tried setting the udev config parameter "udev_log" to "yes" and
> do get logs when other drivers are loaded. However when I do a
> "rmmod admxrc2; modprobe admxrc2" no log information is printed.
>
> 1. Is there a way to get more debug information out of udev ?
> 2. Is there some special thing I need to do in the device module ?
> 3. Is there something wround with the configuration ?
>
> Cheers
>
> Terry
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> 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
Some more information on this:
I have enabled debugiing in the udev sources and now see an error displayed
in the /var/log/messages file:
Jun 3 14:31:07 beam1 udev[15275]: main: looking at '/bus/pci/drivers/admxrc2'
Jun 3 14:31:07 beam1 udev[15275]: main: not a block or class device
This seems to sugest that I need to do something specific in the device
driver module to get udev to work ???
Terry
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
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:[~2005-06-03 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 13:24 Question on how to get custom kernel module to work with udev Terry Barnaby
2005-06-03 13:33 ` Terry Barnaby [this message]
2005-06-03 20:20 ` Kay Sievers
2005-06-04 6:00 ` Terry Barnaby
2005-06-04 6:30 ` Greg KH
2005-06-04 6:32 ` Greg KH
2005-06-04 7:06 ` Terry Barnaby
2005-06-04 7:36 ` Greg KH
2005-06-04 8:14 ` Terry Barnaby
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=42A05C43.5080707@beam.ltd.uk \
--to=terry1@beam.ltd.uk \
--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).