From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug/udev problem
Date: Fri, 14 Jan 2005 09:17:08 +0000 [thread overview]
Message-ID: <1105694228.7556.48.camel@localhost.localdomain> (raw)
In-Reply-To: <1105692480.4134.1.camel@allblack.org>
On Fri, 2005-01-14 at 11:14 +0200, Jan Zwiegers wrote:
> Hi Kay
>
> We develop data acquisition devices (in this case PCI) and use our own
> driver libraries etc, so it does not relate to standard devices.
> We have many drivers (for each series) and I need to create nodes as
> the devices are attached/installed.
> I have developed the driver as suggested by the PCI.txt file under the
> kernel docs, and added the dev (major:minor) sysfs file, which if I
> understand correct udev needs for the node creation.
Ah ok, what does
tree /sys/class/pci_bus/
print?
We skip this class of devices. You need to recompile udev.
--- 1.20/udev_sysfs.c 2004-12-12 00:34:45 +01:00
+++ edited/udev_sysfs.c 2005-01-14 10:12:35 +01:00
@@ -48,7 +48,7 @@
{ .subsystem = "bluetooth", .file = "address" },
{ .subsystem = "firmware", .file = "data" },
{ .subsystem = "i2c-adapter", .file = NULL },
- { .subsystem = "pci_bus", .file = NULL },
+ //{ .subsystem = "pci_bus", .file = NULL },
{ .subsystem = "ieee1394", .file = NULL },
{ .subsystem = "ieee1394_host", .file = NULL },
{ .subsystem = "ieee1394_node", .file = NULL },
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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-01-14 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 8:48 PCI hotplug/udev problem Jan Zwiegers
2005-01-14 9:00 ` Kay Sievers
2005-01-14 9:17 ` Kay Sievers [this message]
2005-01-17 10:40 ` Kay Sievers
2005-01-17 11:38 ` Jan Zwiegers
2005-01-18 17:12 ` Kay Sievers
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=1105694228.7556.48.camel@localhost.localdomain \
--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).