From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: The case of udev and the missing /dev/input/mice
Date: Wed, 21 Sep 2005 17:12:23 +0000 [thread overview]
Message-ID: <d120d50005092110122a4a89b2@mail.gmail.com> (raw)
In-Reply-To: <1127270286.10585.14.camel@localhost.localdomain>
On 9/21/05, Greg KH <greg@kroah.com> wrote:
> On Wed, Sep 21, 2005 at 11:46:31AM -0500, Dmitry Torokhov wrote:
> > On 9/21/05, Greg KH <greg@kroah.com> wrote:
> > >
> > > I have to give a talk about this next week, so I want to have this done
> > > by then so I have something to talk about :)
> > >
> > > So don't worry, I am activly working on it, I have the basics done now,
> > > just trying to get it all to work without oopsing in odd places...
> > >
> >
> > Just remember - release often, release early ;)
>
> Hey, you can always see the current state of my tree, along with this
> work-in-progress on kernel.org in:
> pub/linux/kernel/people/gregkh/gregkh/patches
> if you really are brave :)
>
> > Btw, I see you picked up my "call hotplug earlier" patch but not "pass
> > class_interface" to add()/remove()". Do you have an objection for the
> > later? (It will break I2O unless you have my patch that removes usage
> > of class_interface from there, but other than that it should be fine).
>
> I'm reworking the class_interface stuff right now, so I was going to
> hold off on this to see if it's needed.
>
> Well, why do you need it? You want to have a "generic" class interface?
> Why not individual different ones for every interface type you want to
> use?
>
For input I want to do some actions every time I connect a new
interface to the device and I want to have it done in core. So when a
new interface registers core installs add()/remove() handler which
then calls interface's connect/disconnect handlers. The other way
around would be to program every interface to call into input-core
exported function to finalize connect/disconnect which is not clean
IMHO. I generally prefer the core to control the operation, instead of
leaving it to individual drivers.
> thanks,
>
> greg k-h
>
--
Dmitry
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.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
prev parent reply other threads:[~2005-09-21 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 2:38 The case of udev and the missing /dev/input/mice Scott James Remnant
2005-09-21 9:51 ` Kay Sievers
2005-09-21 11:19 ` Olivier Blin
2005-09-21 12:47 ` Greg KH
2005-09-21 12:53 ` Scott James Remnant
2005-09-21 15:33 ` Dmitry Torokhov
2005-09-21 15:49 ` Greg KH
2005-09-21 16:00 ` Greg KH
2005-09-21 16:11 ` Dmitry Torokhov
2005-09-21 16:33 ` Greg KH
2005-09-21 16:46 ` Dmitry Torokhov
2005-09-21 17:01 ` Greg KH
2005-09-21 17:12 ` Dmitry Torokhov [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=d120d50005092110122a4a89b2@mail.gmail.com \
--to=dmitry.torokhov@gmail.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.