From: "Guo, Min" <min.guo@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: Question about Hot device Identity
Date: Wed, 25 Jun 2003 02:24:43 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105650836122319@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105633765700944@msgid-missing>
Oh, could you please give me an example USB device that udev supported now?
I tried another USB cdrom, I found there are no dev file in /sysfs/class directory.
Whether I need patch kernel.org/pub/linux/kernel/people/gregkh/misc/kobject-hotplug-?-2.5.67.patch
for USB cdrom?
I would like to develop the test suite for Udev firstly, thank you for your kind help.
Thanks
Guo Min
-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Wednesday, June 25, 2003 12:21 AM
To: Guo, Min
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Question about Hot device Identity
On Tue, Jun 24, 2003 at 03:01:21PM +0800, Guo, Min wrote:
> Thanks a lot!
> I am now playing with your udev:-), and I encounter some problems.
>
> I use a usb mouse as a PnP devices, after I mount sysfs, I can not
> find any devices in /sysfs/devices/pci0/00:0f.2 as
> DEVPATH=/devices/pci0/00:09.0/usb1/1-1/1-1.1/ttyUSB7 in the test file
> udev supplied.
>
> 00:0f.2 is my USB controller,
>
> ls /sysfs/devices/pci0/00:0f.2
>
> class irq power subsystem_device vendor
> device name resource subsystem_vendor
>
> So I think the configuration files you given out is for usb hub,is
> that right? For the common USB mouse, can I only configure
> DEVPATH=/sysfs/devices/pci0/00:0f.2? I tried this,but no results.
> Could you please tell me what cause this problem?
What problem? udev only creates dev entries for things that show up in
/sys/class/* that have a file called "dev" in them. Right now, there is
no kernel support for mice under /sys/class/ (but there was a patch
proposed for this posted to linux-kernel by Hanna Linder a few weeks
ago.)
Because of this, udev will not work for your mouse right now, sorry.
So right now my main focus has been providing support in the kernel for
/sys/class for all types of devices, as that is what udev needs. Help
with this effort is greatly appreciated.
thanks,
gre k-h
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
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:[~2003-06-25 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 3:04 Question about Hot device Identity Guo, Min
2003-06-23 3:22 ` Greg KH
2003-06-24 7:01 ` Guo, Min
2003-06-24 16:20 ` Greg KH
2003-06-25 2:24 ` Guo, Min [this message]
2003-06-25 2:33 ` Greg KH
2003-06-25 9:05 ` Guo, Min
2003-06-25 14:45 ` Kevin P. Fleming
2003-06-25 17:00 ` Greg KH
2003-06-26 2:24 ` Guo, Min
2003-06-26 4:10 ` Kevin P. Fleming
2003-06-26 7:42 ` Guo, Min
2003-06-26 17:13 ` Greg KH
2003-06-26 19:05 ` Greg KH
2003-06-26 19:08 ` Greg KH
2003-06-27 2:00 ` Guo, Min
2003-06-27 3:18 ` Greg KH
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=marc-linux-hotplug-105650836122319@msgid-missing \
--to=min.guo@intel.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.