linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [RFC] rfkill/rfkill-input userspace API
Date: Fri, 27 Mar 2009 22:34:49 +0100	[thread overview]
Message-ID: <1238189689.4452.26.camel@johannes.local> (raw)
In-Reply-To: <1238169485-29298-1-git-send-email-hmh@hmh.eng.br> (sfid-20090327_165815_381528_72AF136C)

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Fri, 2009-03-27 at 12:58 -0300, Henrique de Moraes Holschuh wrote:
> This patch set is being posted for comments and ideas.
> 
> It implements a sysfs API for the rfkill core that allows userspace to
> completely implement the operations that rfkill-input is capable of.
> 
> I am not too happy about it, I think it looks ugly.  But I had no
> better ideas.  Comments and ideas for a better one are welcome.

Can we do it after I rewrite the core to be useful wrt. hard/soft
blocks? Same comments as in my other email apply. I'm sorry to waste
your work on it, but on the other hand you clearly didn't ever care
about it enough to have posted it earlier.

> Note: unless something is done to change the way X.org deals with
> input devices, rfkill-input is _useless_ in a large number of setups
> as far as input event handling goes, because it will never get any
> events after X.org evdev grabs the input device.

Right.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-03-27 21:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 15:58 [RFC] rfkill/rfkill-input userspace API Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 1/4] rfkill: prepare to export global states to userspace Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 2/4] rfkill: expose global switches through sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 3/4] rfkill: expose global state to sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 4/4] rfkill: export events for global state changes Henrique de Moraes Holschuh
2009-03-27 21:34 ` Johannes Berg [this message]
2009-03-28 12:37   ` [RFC] rfkill/rfkill-input userspace API Henrique de Moraes Holschuh
2009-03-27 22:11 ` Matthew Garrett
2009-03-28 12:36   ` Henrique de Moraes Holschuh
2009-03-28 12:44     ` Matthew Garrett
2009-03-28 12:47     ` Henrique de Moraes Holschuh
2009-03-28 12:53       ` Matthew Garrett
2009-03-28 14:48         ` Henrique de Moraes Holschuh
2009-03-28 15:02           ` Matthew Garrett
2009-03-28 15:14             ` Henrique de Moraes Holschuh
2009-03-28 15:22               ` Matthew Garrett

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=1238189689.4452.26.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=hmh@hmh.eng.br \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@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).