linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
	linux-input@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH 1/2] input: Add KEY_RFKILL
Date: Wed, 17 Feb 2010 11:54:35 -0800	[thread overview]
Message-ID: <20100217195435.GA15742@core.coreip.homeip.net> (raw)
In-Reply-To: <22ee4e771002171142q1496842ap4079026a5c0be8c6@mail.gmail.com>

On Wed, Feb 17, 2010 at 08:42:45PM +0100, Christian Lamparter wrote:
> On Wed, Feb 17, 2010 at 8:17 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Wed, Feb 17, 2010 at 07:43:56PM +0100, Christian Lamparter wrote:
> >> The reason: Some new devices come with a WPS "Push Button".
> >> And there's no code for them yet.
> >>
> > Yes, we can add a new key definition if you provide clear description of
> > what the intended use is and if we can't map such use to any existing
> > key definitions.
> 
> I found one http://en.wikipedia.org/wiki/Wi-Fi_Protected_Setup (if you
> don't mind):
> 
> There's the relevant part: (PBC stands for Push Button Control/Configuration?)
> 
> "PBC Method, in which the user simply has to push a button, either an actual
> or virtual one, on both the AP (or a Registrar of the Network) and the new
> wireless client device (STA)
> .
> Support of this model is mandatory for APs and optional for STAs."
> 
> And there are already a few potential users:
> OpenWRT routers as well as some rt30xx, ar9170 and ar9271 devices.

Is there anything currently in works that would make use of this button?
I do not want to allocate keycode "for the future" which may never come.
We did it with KEY_BATTERY but I do not think anyone actually uses it.

-- 
Dmitry

  reply	other threads:[~2010-02-17 19:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 21:36 [PATCH 1/2] input: Add KEY_RFKILL Matthew Garrett
2010-02-16 21:36 ` [PATCH 2/2] rfkill: Add support for KEY_RFKILL Matthew Garrett
2010-02-16 23:04   ` Marcel Holtmann
2010-02-16 23:05 ` [PATCH 1/2] input: Add KEY_RFKILL Marcel Holtmann
2010-02-17  5:22 ` Dmitry Torokhov
2010-02-17 18:03   ` Matthew Garrett
2010-02-17 18:43     ` Christian Lamparter
2010-02-17 18:45       ` Matthew Garrett
2010-02-17 18:49         ` Bastien Nocera
2010-02-17 22:34           ` Peter Hutterer
2010-02-18  4:16             ` Dmitry Torokhov
2010-02-18  4:29               ` Peter Hutterer
2010-02-17 19:18         ` Christian Lamparter
2010-02-17 19:17       ` Dmitry Torokhov
2010-02-17 19:42         ` Christian Lamparter
2010-02-17 19:54           ` Dmitry Torokhov [this message]
2010-02-17 20:02             ` Matthew Garrett
2010-02-17 20:49               ` Dmitry Torokhov
2010-02-17 20:50                 ` Matthew Garrett
2010-02-17 20:18             ` Christian Lamparter
2010-02-17 20:52               ` Dmitry Torokhov
2010-02-17 21:12                 ` pat-lkml
2010-02-17 21:28                 ` Christian Lamparter
2010-02-17 21:40                   ` Dmitry Torokhov
2010-02-17 22:03                     ` Christian Lamparter
2010-02-20  9:18                       ` Dmitry Torokhov
2010-02-19 14:33             ` Henrique de Moraes Holschuh
2010-02-17 19:18     ` Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2009-09-10 17:21 Matthew Garrett
2009-09-10 17:27 ` Luis R. Rodriguez
2009-09-10 17:31   ` Matthew Garrett
2009-09-11  5:13 ` Dmitry Torokhov
2009-11-13  5:34   ` Marcel Holtmann

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=20100217195435.GA15742@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=chunkeey@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mjg59@srcf.ucam.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).