From owner-freebsd-current@FreeBSD.ORG Sat Jun 12 01:46:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A606516A4CE for ; Sat, 12 Jun 2004 01:46:36 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33A8143D2D for ; Sat, 12 Jun 2004 01:46:36 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i5C1jAtj017580; Fri, 11 Jun 2004 19:45:10 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 11 Jun 2004 19:45:17 -0600 (MDT) Message-Id: <20040611.194517.98076435.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: "M. Warner Losh" In-Reply-To: <20040611175738.GR51677@cicely12.cicely.de> References: <200406110844.52444.jbarrett@amduat.net> <20040611175738.GR51677@cicely12.cicely.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jbarrett@amduat.net Subject: Re: devd and usb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 12 Jun 2004 01:46:36 -0000 In message: <20040611175738.GR51677@cicely12.cicely.de> Bernd Walter writes: : On Fri, Jun 11, 2004 at 08:44:52AM -0700, Jacob S. Barrett wrote: : > Should the vendor and product codes be accessable in devd. I have seen : > examples while searching Google that suggest that they should be, but they : > don't appear to be. The problem is that I have two devices that get : > recognized as ucom devices, my Visor and my cell phone. Obviously the : > actions I want to purform when they are detected are very different. I tried : > matching based on vendor and product codes, but that doesn't work. The codes : > are not available when devd processes the attach event. : : devd support for usb devices currently don't supply this informations. : I have a patch to add them plus serial numbers, but it's not in : commitable shape yet. : See http://www.bwct.de/usb-devd.patch I have this on my list of things I'd like to get done before 5.3. Warner