From owner-freebsd-usb@FreeBSD.ORG Fri Mar 4 17:47:11 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 007D410656D3 for ; Fri, 4 Mar 2011 17:47:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.c2i.net [212.247.154.130]) by mx1.freebsd.org (Postfix) with ESMTP id 5663F8FC1E for ; Fri, 4 Mar 2011 17:47:09 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=O4luLtK3s/BI/ZI2MixGyL7hJC8Dk2jKRuc55HZ6Kk0= c=1 sm=1 a=KYV0DW-hpPIA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=RKm9piEi1UkfKgC9BvwA:9 a=3BUQuI0ikdnEPngWNv61XeZm2wwA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 94823048; Fri, 04 Mar 2011 18:47:08 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 4 Mar 2011 18:46:46 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <4D7120F5.502@freebsd.org> In-Reply-To: <4D7120F5.502@freebsd.org> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103041846.47008.hselasky@c2i.net> Cc: Andriy Gapon Subject: Re: usbdump not connected to build? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 17:47:11 -0000 On Friday 04 March 2011 18:27:17 Andriy Gapon wrote: > It seems that usbdump not connected to the build? > Is it nor ready yet or something else? > Thanks. Hi, It probably should be connected. The USB trace format is not yet settled and I think that's why. There is some work in progress. --HPS