public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Subject: rfkill-input madness
Date: Fri, 27 Mar 2009 14:06:36 +0100	[thread overview]
Message-ID: <1238159196.4452.1.camel@johannes.local> (raw)

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

The doc says:

        ******IMPORTANT******
        When rfkill-input is ACTIVE, userspace is NOT TO CHANGE THE STATE OF AN RFKILL
        SWITCH IN RESPONSE TO AN INPUT EVENT also handled by rfkill-input, unless it
        has set to true the user_claim attribute for that particular switch.  This rule
        is *absolute*; do NOT violate it.
        ******IMPORTANT******
        
        ...
        
        When rfkill-input is not active, userspace must initiate a rfkill status
        change by writing to the "state" attribute in order for anything to happen.
        


How the hell is userspace supposed to know whether rfkill-input is
active or not? Does anybody fucking care to implement any of this mess
in userspace?

johannes

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

             reply	other threads:[~2009-03-27 13:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 13:06 Johannes Berg [this message]
2009-03-27 14:30 ` rfkill-input madness Henrique de Moraes Holschuh
2009-03-27 21:10   ` Johannes Berg
2009-03-28  0:52     ` Henrique de Moraes Holschuh
2009-03-28 17:50       ` Johannes Berg
2009-03-30 13:23         ` Henrique de Moraes Holschuh
2009-03-30 14:11           ` Johannes Berg
2009-03-30 17:21             ` Henrique de Moraes Holschuh
2009-03-30 17:29               ` Johannes Berg

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=1238159196.4452.1.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=hmh@hmh.eng.br \
    --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