linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: devices with more than one node
Date: Wed, 14 Jan 2004 17:39:31 +0000	[thread overview]
Message-ID: <20040114173931.GE5567@kroah.com> (raw)
In-Reply-To: <20040113193842.GA29887@suse.de>

On Wed, Jan 14, 2004 at 06:29:37PM +0100, Olaf Hering wrote:
>  On Tue, Jan 13, Greg KH wrote:
> 
> > On Tue, Jan 13, 2004 at 10:11:22PM +0100, Olaf Hering wrote:
> > >  On Tue, Jan 13, Greg KH wrote:
> > > > On Tue, Jan 13, 2004 at 08:38:42PM +0100, Olaf Hering wrote:
> > > > > inputdevices have also an event node attached.
> > > > 
> > > > Yes, and you get two different hotplug events, and udev just works,
> > > > right?  (this is with the kernel patches I sent out last week...)
> > > 
> > > I tried the -mm tree, and /proc/bus/input/devices differs indeed. Havent
> > > tried to feed udev with the data.
> > 
> > Look at /sys/class/input in the -mm kernel.  I didn't do anything with
> > the /proc/bus/input stuff.
> 
> I did not load evdev.ko on the other box. Anyway, I havent tested it
> yet, but what will happen with the /dev/input/mice multiplexer and one
> of the 2 USB mice will be removed? I think /dev/input/mice will
> disappear, have to verify that today.

It doesn't do that for me, try testing the code before making such
claims :)

As an example, here's what my /sys/class/input/ looks like with a ps2
and a usb mouse plugged in, and the evdev module loaded:
$ tree /sys/class/input/
/sys/class/input/
|-- event0
|   `-- dev
|-- event1
|   `-- dev
|-- event2
|   |-- dev
|   |-- device -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2.2
|   `-- driver -> ../../../bus/usb/drivers/usb
|-- mice
|   `-- dev
|-- mouse0
|   `-- dev
`-- mouse1
    |-- dev
    |-- device -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2.2
    `-- driver -> ../../../bus/usb/drivers/usb

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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

  parent reply	other threads:[~2004-01-14 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 19:38 devices with more than one node Olaf Hering
2004-01-13 19:46 ` Greg KH
2004-01-13 21:11 ` Olaf Hering
2004-01-13 21:20 ` Greg KH
2004-01-13 23:01   ` Patrick Mansfield
2004-01-13 23:18     ` Greg KH
2004-01-14  1:12       ` dougg
2004-01-14  1:26         ` Greg KH
2004-01-14 17:29 ` Olaf Hering
2004-01-14 17:39 ` Greg KH [this message]
2004-01-14 17:44 ` Greg KH
2004-01-14 19:15 ` Olaf Hering
2004-01-14 21:32 ` Greg KH
2004-01-14 21:35 ` Greg KH
2004-01-15  8:01 ` Vojtech Pavlik
2004-01-15  9:04 ` Olaf Hering
2004-01-15  9:19 ` Vojtech Pavlik
2004-01-15 21: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=20040114173931.GE5567@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).