From: "Guo, Min" <min.guo@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: Question about Hot device Identity
Date: Thu, 26 Jun 2003 02:24:33 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105659452806441@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105633765700944@msgid-missing>
I can not find the file dev in the /sys/class/usb, does it means that
Udev does not support my USB CDROM? If not, which file is behalf of
my USB CDROM device?
you said that udev only creates dev entries for things that show up in
/sys/class/* that have a file called "dev" in them, in my machine,
# ls /sys/
block bus cdev class devices firmware
#ls /sys/class/usb/
#ls /sys/bus/usb/devices/
Both the outputs are null, I think the system has not recognized the USB devices, is that right?
Oh, the second question is whether the patch for Udev to support USB mice
has been applied to kernel 2.5.73?
Thank you very much!
Thanks
Guo Min
-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Thursday, June 26, 2003 1:01 AM
To: Guo, Min
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Question about Hot device Identity
On Wed, Jun 25, 2003 at 05:05:22PM +0800, Guo, Min wrote:
> I download the linux2.5.73 and use USB CDROM to do the testing.
> ls /sysfs
Why /sysfs? Why not /sys like everyone is standardizing on?
> > block bus cdev class devices firmware
> ls /sysfs/class
> >firmware input net pcmcia_socket scsi_device scsi_host tty usb
> ls /sysfs/block
> > fd0 hda initrd sda
> ls /sysfs/devices/pci0
> >0000:00:00.0 0000:00:02.0 0000:00:0f.0 0000:00:0f.2 power
> 0000:00:00.1 0000:00:03.0 0000:00:0f.1 name
> ls /sysfs/devices/pci0/0000\:00\:0f.2/
> >class irq power subsystem_device vendor
> device name resource subsystem_vendor
>
>
> 0000:00:0f.2 is my USB controller.
> So ,in such environment, how to configure DEVPATH in test file?
udev only cares about DEVPATH values for class devices. It ignores
DEVPATH values for other kinds of devices. So set it to your block
device and you should be fine.
> Another question is whether 2.5.73 supports USB mice?
Yes, the kernel does. Even 2.2 does :)
greg 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-26 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
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 [this message]
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-105659452806441@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 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).