From: Stefan Rompf <stefan@loplof.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
netdev@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Re: [RFC PATCH 1/2] Hardware button support for Wireless cards: radiobtn
Date: Sun, 4 Jun 2006 12:14:45 +0200 [thread overview]
Message-ID: <200606041214.45999.stefan@loplof.de> (raw)
In-Reply-To: <200606041002.33696.IvDoorn@gmail.com>
Am Sonntag 04 Juni 2006 10:02 schrieb Ivo van Doorn:
> Except for the bluetooth radio key (which should be supported by the
> radiobtn interface as well) the other buttons have support through already
> excisting input devices if I am correct.
You are wrong for quite a bunch of laptop models. That's why I pointed you to
the wistron_btns driver. Alternatively, look at the acerhk driver
(http://www2.informatik.hu-berlin.de/~tauber/acerhk/). Many systems have a
number of additional buttons that need to be handled by a special driver, all
sent to userspace, and just one of them to trigger the wireless card. Other
models just handle the button in ACPI and generate an additional ACPI event.
Looking at the RT2400-driver, I see what you want to accomplish: Take the view
of the WLAN card on the hardware controlled button enable/disable and
generate events on it. However, in many cases it is another driver (see
above) that sets or clears this state, and this should be the instance to
send the input event.
Note that I do not have objections against the driver being included in the
kernel - it just does not qualify as generic radiobutton support, but I know
it's hard to find a good name ;-)
Looking at the code only: There should be an additional non-polling interface
for drivers that can generate events on the own.
Stefan
next prev parent reply other threads:[~2006-06-04 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 15:16 [RFC PATCH 1/2] Hardware button support for Wireless cards: radiobtn Ivo van Doorn
2006-05-29 15:58 ` Ivo van Doorn
2006-05-30 21:43 ` Francois Romieu
2006-05-31 17:31 ` Ivo van Doorn
2006-05-31 18:05 ` Ivo van Doorn
2006-06-02 14:30 ` Ivo van Doorn
2006-06-03 8:45 ` Stefan Rompf
2006-06-04 8:02 ` Ivo van Doorn
2006-06-04 10:14 ` Stefan Rompf [this message]
2006-06-04 11:44 ` Ivo van Doorn
2006-06-17 15:05 ` Ivo van Doorn
2006-06-22 15:55 ` Jiri Benc
2006-06-23 11:08 ` Vojtech Pavlik
2006-06-23 18:51 ` Ivo van Doorn
2006-06-23 19:32 ` Vojtech Pavlik
2006-06-23 21:35 ` Ivo van Doorn
2006-06-23 18:53 ` Ivo van Doorn
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=200606041214.45999.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=ivdoorn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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).