From: Justin Clacherty <justin@redfish-group.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rule for custom driver
Date: Tue, 19 Dec 2006 01:19:15 +0000 [thread overview]
Message-ID: <45873E13.8090108@redfish-group.com> (raw)
In-Reply-To: <45873525.8050007@redfish-group.com>
Thanks Alex.
Alex Merry wrote:
> The original kernel name is spi1.0. Do you get /dev/spi1.0 created already (ie: even without the rule)?
I thought it should automagically create /dev/spi1.0 but it doesn't.
> One other thing to check, though, is whether /sys/devices/platform/pxa2xx-spi.1/spi1.0/dev exists (it should have a major:minor pair to tell udev how to create the device).
>
No, this doesn't exist, I guess that's the problem. I can manually
create the node and it works fine but if the major number changes (it's
dynamic) then I'll have some problems - thus udev. Looks like it's time
to find out how to create the dev entry in /sys. If anyone can help by
pointing me to appropriate documents or code that'd be great.
Justin.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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-12-19 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 0:41 udev rule for custom driver Justin Clacherty
2006-12-19 0:53 ` Alex Merry
2006-12-19 1:19 ` Justin Clacherty [this message]
2006-12-19 3:33 ` Justin Clacherty
2006-12-19 7:31 ` 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=45873E13.8090108@redfish-group.com \
--to=justin@redfish-group.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.