linux-kernel - Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Aug 2008 23:58:40 -0700
From:	Philip Langdale <philipl@...rt.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	toshiba_acpi@...ebeam.org, Ivo van Doorn <ivdoorn@...il.com>,
	linux-wireless@...r.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling
 through rfkill (v2)

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

--
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/