All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Sysfs properties with libudev (for example capabilities/key)
Date: Sun, 31 Oct 2010 20:54:21 +0000	[thread overview]
Message-ID: <20101031205421.GA31298@kroah.com> (raw)
In-Reply-To: <AANLkTi=z2McbB95XxgZ5kFoojeLVOGWHfYQCtLFJfw3e@mail.gmail.com>

On Sun, Oct 31, 2010 at 09:09:03AM -0700, Laszlo Papp wrote:
> Hi,
> 
> My further question is that whether libudev can help me to handle
> input events, like keyboard, mouse, touch presses ?

No, that is what x.org is for.

> What is the best to do that in a userspace input system where I would
> like to avoid the 'root' usage, 'root' privileges so that simple users
> can use it.

See the x.org input subsystem code for examples of how to do this.

good luck,

greg k-h

      parent reply	other threads:[~2010-10-31 20:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 21:17 Sysfs properties with libudev (for example capabilities/key) Laszlo Papp
2010-10-30 21:23 ` Laszlo Papp
2010-10-31  1:39 ` Greg KH
2010-10-31 14:04 ` Laszlo Papp
2010-10-31 14:23 ` Greg KH
2010-10-31 14:39 ` Laszlo Papp
2010-10-31 14:52 ` Laszlo Papp
2010-10-31 16:09 ` Laszlo Papp
2010-10-31 20:54 ` Greg KH [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=20101031205421.GA31298@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 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.