From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 6 21:49:25 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BFD6C2F for ; Tue, 6 Jan 2015 21:49:25 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F192D660F7 for ; Tue, 6 Jan 2015 21:49:24 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 866241FE022; Tue, 6 Jan 2015 22:49:22 +0100 (CET) Message-ID: <54AC5892.5000308@selasky.org> Date: Tue, 06 Jan 2015 22:50:10 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Mason Loring Bliss Subject: Re: usbhidctl / Logitech References: <20150106000213.GT4187@blisses.org> <54AB8F81.8070702@selasky.org> <20150106165926.GU4187@blisses.org> In-Reply-To: <20150106165926.GU4187@blisses.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2015 21:49:25 -0000 On 01/06/15 17:59, Mason Loring Bliss wrote: > On Tue, Jan 06, 2015 at 08:32:17AM +0100, Hans Petter Selasky wrote: > >> Did you checkout "sysutils/uhidd" in ports yet? > > The docs say: > > "Note that before you can use uhidd with certain ugenX.Y device, you need > to make sure there is no kernel HID device driver attached to that > device. You could either remove 'device ukbd', 'device ums' and 'device > uhid' from your kernel config file and recomplie the kernel, or if these > drivers are loaded as kernel modules, kldunload(8) them." > > It would be unfortunate to have to build a custom kernel and resort to > something from ports when the in-tree tool is one bugfix away from supporting > my hardware perfectly. > > I guess I need to understand more of the background to figure out what the > most reasonable fix would be. I'll do some more research. > I think "uhidd" will detach any kernel drivers it finds? Did you try it? --HPS