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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Aug 2008 06:29:08 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Philip Langdale <philipl@...rt.org>
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)

On Mon, 11 Aug 2008, Philip Langdale wrote:
> Henrique de Moraes Holschuh wrote:
>> Hmm?  UNBLOCKED means it is not being rfkilled.  Why is not working?  Put
>> some debug printks on your toggle_radio callback, that might help fix the
>> issue...
>
> Well, what I see is this:
>
> At modprobe, I get an explicit unblock request. When I modify 'state' in sysfs,
> I see appropriate requests to soft block and unblock. When I activate the hardware
> kill switch, the rfkill state goes to hard_block but no one calls toggle_radio
> and when I release the kill switch, the state goes to soft_block and no one
> calls toggle_radio.

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).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/