From: reinette chatre <reinette.chatre@intel.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi (4965) regression since 2.6.30
Date: Fri, 14 Aug 2009 09:07:47 -0700 [thread overview]
Message-ID: <1250266067.30019.6376.camel@rc-desk> (raw)
In-Reply-To: <20090814021031.GB4555@khazad-dum.debian.net>
On Thu, 2009-08-13 at 19:10 -0700, Henrique de Moraes Holschuh wrote:
> On Thu, 13 Aug 2009, reinette chatre wrote:
> > On Fri, 2009-08-07 at 14:35 -0700, Lukas Hejtmanek wrote:
> > > On Thu, Aug 06, 2009 at 08:07:04PM -0300, Henrique de Moraes Holschuh wrote:
> > > > On Fri, 07 Aug 2009, Lukas Hejtmanek wrote:
> > > > > 0x0004 = 238 # KEY_WLAN
> > > >
> > > > This means any rfkill input handler (be it in kernel or userspace) will
> > > > toggle your WLAN cards when fn+f5 is pressed. You can just assign a
> > > > different keycode to it (use KEY_RESERVED or KEY_UNKNOWN if you don't want
> > > > the key to do anything).
> > >
> > > Could you give me some hints how to do the mapping?
> >
> > On my system this key is mapped to 385 (KEY_RADIO) - so that can explain
>
> And KEY_RADIO is the key to select the radio tuner... heh. The
> bogosity never ends. At least it is unlikely that anything would care
> for KEY_RADIO.
On my system this key toggles bluetooth rfkill and does not touch wifi.
I think this is what Lukas wants it to do. I thus hope when he sets his
key mapping to KEY_RADIO he will get the same behavior.
> > >From what I understand you can use input-kbd to change the key mappings.
> > The map file you can provide to it is in same format as the one it
> > prints for you.
>
> You can also add a HAL fdi file. I will attach one I found on my
> system, modify to your taste and find out where you should drop it on
> /etc for HAL to use...
Thanks!
Reinette
next prev parent reply other threads:[~2009-08-14 16:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 7:57 iwlwifi (4965) regression since 2.6.30 Lukas Hejtmanek
2009-07-27 16:03 ` reinette chatre
2009-07-27 16:06 ` Johannes Berg
2009-07-28 11:21 ` Lukas Hejtmanek
2009-07-28 12:54 ` Johannes Berg
2009-08-02 22:12 ` Lukas Hejtmanek
2009-08-03 21:47 ` reinette chatre
2009-08-04 8:49 ` Lukas Hejtmanek
2009-08-04 22:49 ` reinette chatre
2009-08-04 22:56 ` Lukas Hejtmanek
2009-08-04 23:38 ` reinette chatre
2009-08-06 13:22 ` Henrique de Moraes Holschuh
2009-08-06 22:41 ` Lukas Hejtmanek
2009-08-06 23:07 ` Henrique de Moraes Holschuh
2009-08-07 20:32 ` Johannes Stezenbach
2009-08-07 21:16 ` Lukas Hejtmanek
2009-08-07 21:35 ` Lukas Hejtmanek
2009-08-13 22:59 ` reinette chatre
2009-08-14 2:10 ` Henrique de Moraes Holschuh
2009-08-14 16:07 ` reinette chatre [this message]
2009-07-27 16:07 ` 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=1250266067.30019.6376.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/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.