linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kai Hendry <hendry@iki.fi>, linux-wireless@vger.kernel.org
Subject: Re: rfkill bound to a switch
Date: Mon, 01 Aug 2016 11:16:01 +0200	[thread overview]
Message-ID: <1470042961.3389.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1469692952.331455.679081257.3C81B1F3@webmail.messagingengine.com> (sfid-20160728_100238_835650_2A9D839C)

On Thu, 2016-07-28 at 16:02 +0800, Kai Hendry wrote:
> Hi there,
> 
> Since laptops typically have a toggle button for killing and enabled
> wifi, how does one supposed to bind rfkill like a toggle?
> 
> I.e. knowing which state you are in so you can call {block,unblock}
> accordingly?
> 
> Parsing event or list output seems non-trivial.
> 

Don't use the rfkill tool - just open /dev/rfkill yourself, the API is
really simple.

johannes

      reply	other threads:[~2016-08-01  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  8:02 rfkill bound to a switch Kai Hendry
2016-08-01  9:16 ` Johannes Berg [this message]

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=1470042961.3389.6.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hendry@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    /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).