[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d120d5000612061410l3f4e0c4x60c5456c17ef4d61@mail.gmail.com>
Date: Wed, 6 Dec 2006 17:10:56 -0500
From: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
To: "Jiri Benc" <jbenc@...e.cz>
Cc: "Ivo van Doorn" <ivdoorn@...il.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, "John Linville" <linville@...driver.com>,
"Lennart Poettering" <lennart@...ttering.net>,
"Johannes Berg" <johannes@...solutions.net>,
"Larry Finger" <Larry.Finger@...inger.net>
Subject: Re: [RFC] rfkill - Add support for input key to control wireless radio
On 12/6/06, Jiri Benc <jbenc@...e.cz> wrote:
> On Wed, 6 Dec 2006 15:18:12 -0500, Dmitry Torokhov wrote:
> > On 12/6/06, Ivo van Doorn <ivdoorn@...il.com> wrote:
> > > Ok, so input device opening should not block the rfkill signal and the rfkill handler
> > > should still go through with its work unless a different config option indicates that
> > > userspace wants to handle the event.
> >
> > I don't think a config option is a good idea unless by config option
> > you mean a sysfs attribute.
>
> What about using EVIOCGRAB ioctl for this?
>
Will not work when the button is on your USB keyboard ;)
--
Dmitry
-
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