From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Coding problem with sysfs
Date: Mon, 07 Jun 2004 23:38:20 +0000 [thread overview]
Message-ID: <20040607233820.GA11689@kroah.com> (raw)
In-Reply-To: <002c01c44883$2717bfc0$0600a8c0@blackbox>
On Sat, Jun 05, 2004 at 06:23:25PM +0200, Christian Gmeiner wrote:
> >
> > Anyway, how are you putting struct class_device structures into such a
> > tree? We don't currently allow parents of them in the kernel. Are you
> > using basic kobjects here?
> Yep i am using kobjects to this. I need this structure, because there can be
> more than one adapter.
> At the moment i able to get some infos like:
> vdr root # cat /sys/class/dvb/adapter0/name
> KNC1 DVB-S
> vdr root # cat /sys/class/dvb/adapter0/frontend
> STV0299/TSA5059/SL1935 based
That's fine. It's the subdirectories underneath the
/sys/class/dvb/adapter0/ directory that will not work.
You are attaching class_device structures by messing with the kobject
parent pointer. Sorry, but we don't support that just yet in the driver
model. Stick with a 1 level deep directory for device that have a "dev"
file, or send in patches to the driver core :)
> > What hotplug events get generated when you create your "demux0" and
> > others devices?
> How can i check the hotplug events? I have here an PCI-DVB card.
Enable DEBUG for the lib/kobject.c file. That will spit out the hotplug
events to the syslog debug file.
Make sure when your device is added (modprobed or whatever) the hotplug
event is getting generated. If so, udev should pick it up if it is
installed properly.
Good luck.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
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
prev parent reply other threads:[~2004-06-07 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 9:21 Coding problem with sysfs Christian Gmeiner
2004-06-04 21:05 ` Greg KH
2004-06-05 0:30 ` Christian Gmeiner
2004-06-05 15:40 ` Greg KH
2004-06-05 16:23 ` Christian Gmeiner
2004-06-07 23:38 ` Greg KH [this message]
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=20040607233820.GA11689@kroah.com \
--to=greg@kroah.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).