[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805202035.20529.inaky@linux.intel.com>
Date: Tue, 20 May 2008 20:35:19 -0700
From: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
To: Henrique de Moraes Holschuh <hmh@....eng.br>
Cc: Ivo van Doorn <ivdoorn@...il.com>, linux-kernel@...r.kernel.org,
Thomas Renninger <trenn@...e.de>,
"John W. Linville" <linville@...driver.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 09/15] rfkill: add the WWAN radio type
On Tuesday 20 May 2008, Henrique de Moraes Holschuh wrote:
> On Tue, 20 May 2008, Ivo van Doorn wrote:
> > On Sunday 18 May 2008, Henrique de Moraes Holschuh wrote:
> > > Add a WWAN rfkill type for generic wireless WAN devices. No keys are added
> > > as most devices really want to use KEY_WLAN for WWAN control (in a cycle of
> > > none, WLAN, WWAN, WLAN+WWAN) and need no specific keycode added.
> > >
> > > Signed-off-by: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
BTW, I just realized this was mistakenly put in your initial patch;
you signed off for me and also added me to the CC :)
> Stuff like "WiMax", "802.1a", "EDGE", "GRPS", "802.1bg" would be the
> type, and class would be "WLAN", "WWAN", etc.
>
> We would only deal with classes on rfkill-input. Anything else more
> specific should be done in userspace instead, disabling rfkill-input.
How would this apply to the case where I want to use the HW key to switch
one off and turn the other one off (say I have both a WiMAX and EDGE
cards in my machine); how could we do it to distinguish which key is which?
I might be missing something.
--
Inaky
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists