All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: devices with more than one node
Date: Wed, 14 Jan 2004 19:15:42 +0000	[thread overview]
Message-ID: <20040114191542.GA3858@suse.de> (raw)
In-Reply-To: <20040113193842.GA29887@suse.de>

 On Wed, Jan 14, Greg KH wrote:

> 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 :)

/dev/input/mice has no real device behind it, so it is safe. Can you add
that to udev.rules to keep compatibility?

# input devices
KERNEL="mice",           NAME="input/%k"
KERNEL="keyboard",       NAME="input/%k"
KERNEL="mouse*",         NAME="input/%k"
KERNEL="event*",         NAME="input/%k"


-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, n√úRNBERG


-------------------------------------------------------
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 19:15 UTC|newest]

Thread overview: 27+ 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:01     ` Patrick Mansfield
2004-01-13 23:18     ` Greg KH
2004-01-13 23:18       ` Greg KH
2004-01-14  1:12       ` dougg
2004-01-14  1:12         ` dougg
2004-01-14  1:26         ` Greg KH
2004-01-14  1:26           ` Greg KH
2004-01-14  3:08         ` Willem Riede
2004-01-15  8:04           ` Douglas Gilbert
2004-01-15 23:21             ` Greg KH
2004-01-16  9:59               ` Mike Anderson
2004-01-18 22:08             ` Willem Riede
2004-01-14 17:29 ` Olaf Hering
2004-01-14 17:39 ` Greg KH
2004-01-14 17:44 ` Greg KH
2004-01-14 19:15 ` Olaf Hering [this message]
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=20040114191542.GA3858@suse.de \
    --to=olh@suse.de \
    --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.