From owner-freebsd-usb@freebsd.org Fri Jul 22 18:00:52 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37288BA18CA for ; Fri, 22 Jul 2016 18:00:52 +0000 (UTC) (envelope-from hps@selasky.org) 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 01D8C18E9 for ; Fri, 22 Jul 2016 18:00:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (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 805711FE022; Fri, 22 Jul 2016 20:00:49 +0200 (CEST) Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU To: Karl Denninger , freebsd-usb@freebsd.org References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <2e196c65-1de6-3627-9bd8-633763727a55@denninger.net> From: Hans Petter Selasky Message-ID: <58fa3f8a-cb10-7757-b5a8-862ae76770de@selasky.org> Date: Fri, 22 Jul 2016 20:04:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <2e196c65-1de6-3627-9bd8-633763727a55@denninger.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 18:00:52 -0000 On 07/22/16 19:16, Karl Denninger wrote: > What do you think about my screwing with the driver to provide a > modest-sized dynamic stack that would use the sysctl interface to > add/delete vendor/product pairs for this purpose? With a modest but > reasonable limit this then becomes something that can be used in a > production environment since you probably would have a modest number of > these devices on USB for any particular individual system and now you > don't have to futz with the kernel to add/remove them. > > I implemented an application read/write piece to a ugen-attached device > but it would have been nice to be able to poke this instead via such a > "hook"; if I write it and submit it as a PR what do people think about > its odds of being committed? Hi, It has been suggested to extend the quirks subsystem, to be able to add custom attach / detach rules to central USB device drivers. --HPS