From: Greg KH <greg@kroah.com>
To: Daniel Drake <dsd@laptop.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org,
hadess@hadess.net, Carlos Garnacho <carlosg@gnome.org>
Subject: Re: Communicating tablet mode status to userspace
Date: Wed, 03 Oct 2012 15:05:42 +0000 [thread overview]
Message-ID: <20121003150542.GA8460@kroah.com> (raw)
In-Reply-To: <CAMLZHHQfGuiK6s_d8ya8FUNiDiGDpgh35VFbHcu-mgCH-=TXVw@mail.gmail.com>
On Wed, Oct 03, 2012 at 08:52:31AM -0600, Daniel Drake wrote:
> On Tue, Oct 2, 2012 at 5:36 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Why can't you change event device ownership to the local user? Then you
> > can read and act upon events.
>
> That would work, I guess.
>
> However, it sounds like your suggesting that we add some custom rules
> in OLPC's own builds and leave it at that. I'm not sure what
> user/group we could use for a generic rule matching this hardware.
That shouldn't be a custom rule, other distros bind the keyboard / mouse
to the local user in order to handle the multi-seat situation properly.
That should all be done already in the console-kit logic (or whatever
handles it now.)
Have you looked into that?
greg k-h
next prev parent reply other threads:[~2012-10-03 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 22:27 Communicating tablet mode status to userspace Daniel Drake
2012-10-02 22:39 ` Alan Cox
2012-10-02 23:36 ` Dmitry Torokhov
2012-10-03 2:58 ` Greg KH
2012-10-03 14:52 ` Daniel Drake
2012-10-03 15:05 ` Greg KH [this message]
2012-10-03 15:23 ` Kay Sievers
2012-10-03 16:04 ` Daniel Drake
2012-10-05 15:50 ` Bastien Nocera
2012-10-05 16:11 ` Daniel Drake
2012-10-05 16:40 ` Bastien Nocera
2012-10-04 13:35 ` Mark Brown
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=20121003150542.GA8460@kroah.com \
--to=greg@kroah.com \
--cc=carlosg@gnome.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dsd@laptop.org \
--cc=hadess@hadess.net \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-input@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).