From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 18 15:47:04 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09053E5A for ; Sun, 18 Jan 2015 15:47:04 +0000 (UTC) Received: from phlegethon.blisses.org (phlegethon.blisses.org [50.56.97.101]) (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 DC50CC72 for ; Sun, 18 Jan 2015 15:47:03 +0000 (UTC) Received: from blisses.org (cocytus.blisses.org [23.25.209.73]) by phlegethon.blisses.org (Postfix) with ESMTPSA id 2B3A114895A; Sun, 18 Jan 2015 10:38:27 -0500 (EST) Date: Sun, 18 Jan 2015 10:38:25 -0500 From: Mason Loring Bliss To: Jan Beich Subject: Re: usbhidctl / Logitech Message-ID: <20150118153825.GG4474@blisses.org> References: <20150106000213.GT4187@blisses.org> <54AB8F81.8070702@selasky.org> <20150106165926.GU4187@blisses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Hans Petter Selasky , 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: Sun, 18 Jan 2015 15:47:04 -0000 On Sun, Jan 18, 2015 at 03:12:01PM +0100, Jan Beich wrote: > Otherwise, add forced_attach=YES to uhidd.conf after applying > https://code.google.com/p/uhidd/source/detail?r=215 Why would I want to do this, though? I don't understand. Please explain. I want to fix usbhidaction specifically. I've got a workaround in the code that makes *my* device work for *me*, but it's not an appropriate fix for general consumption, as it ignores the device's declaration that it returns a range. I think what I need to do is to write to the original authors of the code and get some pointers about intent, and if this is misbehaviour in the device and not the code, I need to see about adding to or imlementing quirk tables of some sort. I'll try to put together some information later today to do just this, since I've gotten lazy as a result of my work-around working for me. It's still broken for everyone else, and my "fix" is incorrect in any event. I appreciate your time in responding, in any event. If you have any insights into uhid devices declaring a range when they evidently don't use one, I'd love to hear them. My Logitech keyboard generates static values on these key- presses, and they're lost when they go through the range converter, but forcing the code to ignore ranges all the time will doubtless break other devices that do use them. -- Mason Loring Bliss mason@blisses.org Ewige Blumenkraft! awake ? sleep : random() & 2 ? dream : sleep; -- Hamlet, Act III, Scene I