From owner-freebsd-current@FreeBSD.ORG Sun Dec 27 19:26:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E70E31065672 for ; Sun, 27 Dec 2009 19:26:48 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id A3F088FC1E for ; Sun, 27 Dec 2009 19:26:48 +0000 (UTC) Received: from maja.lab.techwires.net (dslb-088-065-053-175.pools.arcor-ip.net [88.65.53.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id CA180192FCB for ; Sun, 27 Dec 2009 20:26:46 +0100 (CET) Received: from maja.lab.techwires.net (localhost [127.0.0.1]) by maja.lab.techwires.net (8.14.3/8.14.3) with ESMTP id nBRJQfkG002330 for ; Sun, 27 Dec 2009 20:26:41 +0100 (CET) (envelope-from bschmidt@techwires.net) Received: (from bschmidt@localhost) by maja.lab.techwires.net (8.14.3/8.14.3/Submit) id nBRJQd4L002329 for freebsd-current@freebsd.org; Sun, 27 Dec 2009 20:26:39 +0100 (CET) (envelope-from bschmidt@techwires.net) X-Authentication-Warning: maja.lab.sad1.techwires.net: bschmidt set sender to bschmidt@techwires.net using -f From: Bernhard Schmidt To: freebsd-current@freebsd.org Date: Sun, 27 Dec 2009 20:26:39 +0100 User-Agent: KMail/1.12.4 (FreeBSD/9.0-CURRENT; KDE/4.3.4; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200912272026.39782.bschmidt@techwires.net> Subject: CFR: rfkill facility X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2009 19:26:49 -0000 Hi, I've spend quite bit of time to get the RF kill switch handling correct while working on iwn(4). During that I have noticed that almost every driver has its own quirks to get things done and that there is no way to get the state exposed to the user. An interface for that might address those issues. I had some spare time and put a few things together: http://techwires.net/~bschmidt/patches/freebsd/rfkill/ With that and just a few modifications to a driver, e.g. for iwn(4) http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_rfkill.diff we can get a more desirable outcome. maja:~# rfkill RFID Device Type Hard Soft 1 iwn0 WLAN no no -- Bernhard