Re: [PATCH 09/15] rfkill: add the WWAN radio type

From: Henrique de Moraes Holschuh
Date: Wed May 21 2008 - 10:07:57 EST

On Tue, 20 May 2008, Inaky Perez-Gonzalez wrote:
> On Tuesday 20 May 2008, Henrique de Moraes Holschuh wrote:
> > On Tue, 20 May 2008, Inaky Perez-Gonzalez wrote:
> > > > 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.
> >
> > I don't understand. Switch one off and turn the other one off? Isn't
> > that the same thing?
> -EOPERATORISDUMB, sorry; I meant turn one off and the other on.

Then here's what you'd have with (class, type):


1. rfkill-input would manipulate based on class for a given input event.
Therefore we would remove KEY_WIMAX from rfkill-input.


2. rfkill-input would be teached to manipulate for classes (all switches
in a class), and for (class,type) (hunt down all rfkill switches of that given
type and class)... and it does mean KEY_WIMAX would only affect WiMAX
switches, while WWAN would affect EDGE, GPRS, *WIMAX*, etc.

And if you need anything different, you'd have to do it in userspace as
you want, and disable rfkill-input entirely, or for the switches you
want to override (using user_claim).

"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at