From: Jan Niehusmann <jan@gondor.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: cm4000 device creation again
Date: Fri, 07 Apr 2006 13:58:51 +0000 [thread overview]
Message-ID: <e15r6r$ovk$1@sea.gmane.org> (raw)
In-Reply-To: <1142167169.5920.3.camel@otto.ehbuehl.net>
Greg KH wrote:
> On Thu, Apr 06, 2006 at 04:02:26PM +0200, Harald Welte wrote:
>> cmm_class = class_create(THIS_MODULE, "cardman_4000");
>> major = register_chrdev(0, DEVICE_NAME, &cm4000_fops);
>> class_device_create(cmm_class, NULL, MKDEV(major, i), NULL, "cmm%d", i);
>>
>> where 'i' is the minor number.
>
> Hm, that seems just fine. And no "dev" file is being created in the
> sysfs directory? That should work...
Maybe the code is in the wrong location or doesn't get called for some
other reason? I observed the following:
If I have the card plugged in at bootup, no /dev/cmm0 gets created, and
/sys/class/cardman_4000/cmm0/ only contains uevent, no file called dev.
But if I first load the cm4000_cs module manually and plug in the card
after that, both /sys/class/cardman_4000/cmm0/dev and /dev/cmm0 appear.
So it looks to me like either class_device_create doesn't get called if
the cm4000_cs gets loaded in response to the card being inserted, or it
does get called but doesn't work because something else is not yet
properly initialized at that time.
Does that make sense?
Jan
-------------------------------------------------------
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-07 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 12:39 cm4000 device creation again Joachim Breitner
2006-03-13 7:02 ` Kay Sievers
2006-03-13 21:33 ` Joachim Breitner
2006-04-02 20:58 ` Joachim Breitner
2006-04-04 17:01 ` Greg KH
2006-04-06 13:57 ` Harald Welte
2006-04-06 14:02 ` Harald Welte
2006-04-06 14:53 ` Greg KH
2006-04-06 16:21 ` Joachim Breitner
2006-04-07 13:58 ` Jan Niehusmann [this message]
2006-04-07 14:25 ` Jan Niehusmann
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='e15r6r$ovk$1@sea.gmane.org' \
--to=jan@gondor.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 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).