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:00:33 +0000 [thread overview]
Message-ID: <1105693234.7556.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1105692480.4134.1.camel@allblack.org>
On Fri, 2005-01-14 at 10:48 +0200, Jan Zwiegers wrote:
> Hi All
>
> I'm running FC3 and is busy updating PCI drivers (with all the latest
> PCI API goodies) to utilize the new udev system.
>
> udevinfo tells me the following:
>
> looking at class device
> '/sys/class/pci_bus/0000:02/bridge/0000:02:02.0':
> SYSFS{class}="0x110000"
> SYSFS{detach_state}="0"
> SYSFS{dev}="254:0"
> SYSFS{device}="0x0041"
> SYSFS{drivername}="pci76xdrv0"
> SYSFS{irq}="9"
> SYSFS{serial}="1000000063"
> SYSFS{subsystem_device}="0x0000"
> SYSFS{subsystem_vendor}="0x0000"
> SYSFS{vendor}="0xea01"
>
> I have the following rule:
>
> SYSFS{drivername}="pci76xdrv0", NAME="pci76xdrv0"
>
> in
>
> /etc/udev/rules.d/50-udev.rules
>
> The problem is udev does not create my new node.
What kind of device do you expect under the pci_bus class, normally
there are no nodes to create for?
Kay
-------------------------------------------------------
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:00 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 [this message]
2005-01-14 9:17 ` Kay Sievers
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=1105693234.7556.40.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).