From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Will Keaney <keaneyw@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v11] rfkill: rewrite
Date: Wed, 27 May 2009 14:04:31 -0400 [thread overview]
Message-ID: <1243447471.17301.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20090527080737.GB8134@tuxdriver.com>
On Wed, 2009-05-27 at 10:07 +0200, John W. Linville wrote:
> On Tue, May 26, 2009 at 11:55:16PM -0300, Henrique de Moraes Holschuh wrote:
> > On Tue, 26 May 2009, John W. Linville wrote:
> > > On Tue, May 26, 2009 at 08:19:29AM -0400, Will Keaney wrote:
> > > > Johannes Berg wrote:
> > > > > This patch completely rewrites the rfkill core to address
> > > > > the following deficiencies:
> > > > >
> > > > I applied this to a fresh pull of wireless-testing this morning, and
> > > > haven't had any problems from it. It looks like the soft lockup I
> > > > reported earlier has been fixed.
> > >
> > > Cool, thanks for the report.
> > >
> > > I'm leaning towards merging this in time for the 2.6.31 merge
> > > window...who wants to complain? :-)
> >
> > As long as the missing userspace control functionality (the lack of which is
> > a _serious_ regression for platform drivers) is added before 2.6.31 ships, I
> > have no complains.
> >
> > Userspace must be able to change the (soft) state using sysfs. This is
> > not an optional part of rfkill :-)
>
> Are there any apps that actually use this feature? It seems like
> that even if there are apps, they need to handle drivers that don't
> support it.
I'd use it NM for the "Enable Wireless" checkbox. The alternative is
SIOCSIWTXPOW -> off I guess, though it would be nicer to just talk to
one thing in sysfs instead of listen to one and SIWTXPOW to set.
Dan
next prev parent reply other threads:[~2009-05-27 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 21:52 [PATCH v10] rfkill: rewrite Johannes Berg
2009-05-23 8:44 ` [PATCH v11] " Johannes Berg
2009-05-26 12:19 ` Will Keaney
2009-05-26 13:15 ` John W. Linville
2009-05-26 13:32 ` Dan Williams
2009-05-26 13:48 ` Marcel Holtmann
2009-05-27 2:55 ` Henrique de Moraes Holschuh
2009-05-27 6:28 ` Johannes Berg
2009-05-27 14:00 ` Henrique de Moraes Holschuh
2009-05-27 14:24 ` Johannes Berg
2009-05-27 19:21 ` Henrique de Moraes Holschuh
2009-05-27 8:07 ` John W. Linville
2009-05-27 14:05 ` Henrique de Moraes Holschuh
2009-05-27 18:04 ` Dan Williams [this message]
2009-05-26 13:27 ` Johannes Berg
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=1243447471.17301.21.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=keaneyw@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).