From: Philip Langdale <philipl@overt.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org, Ivo van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2)
Date: Wed, 13 Aug 2008 23:58:40 -0700 [thread overview]
Message-ID: <48A3D7A0.7010704@overt.org> (raw)
In-Reply-To: <20080813092908.GA6806@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
>
> Looks like either rfkill-input is inactive, or something is binding to the
> toshiba_acpi input device and setting it to exclusive mode (X evdev does
> this).
Almost. Turns out there were two problems:
1) I was setting SW_RFKILL_ALL as a keybit instead of an swbit - so no
events reported. Whoops. :-)
2) Maybe this shouldn't surprise me, but the expected switch semantics
are that '1' means radios are on and 0 means they are killed - I thought
it was the other way round.
Now, when I release the kill switch, rfkill-input does indeed turn the
radio on. Great. The remaining problem is that rfkill-input is setting
it to soft-blocked when the switch is registered. I'm not sure why it's
deciding to do that. Anyway, I'm almost there. Thanks.
--phil
next prev parent reply other threads:[~2008-08-14 6:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 19:12 [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2) Philip Langdale
2008-08-03 4:26 ` Henrique de Moraes Holschuh
2008-08-04 1:10 ` Philip Langdale
2008-08-05 21:24 ` Henrique de Moraes Holschuh
2008-08-06 3:33 ` Philip Langdale
2008-08-06 12:26 ` Henrique de Moraes Holschuh
2008-08-06 12:45 ` Henrique de Moraes Holschuh
2008-08-07 4:40 ` Philip Langdale
2008-08-07 13:45 ` Henrique de Moraes Holschuh
2008-08-11 16:41 ` Philip Langdale
2008-08-13 9:29 ` Henrique de Moraes Holschuh
2008-08-14 6:58 ` Philip Langdale [this message]
2008-08-16 19:22 ` Philip Langdale
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=48A3D7A0.7010704@overt.org \
--to=philipl@overt.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=toshiba_acpi@memebeam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.