From owner-freebsd-usb@FreeBSD.ORG Tue Jan 20 21:43:44 2015 Return-Path: Delivered-To: freebsd-usb@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 A56D7F4F for ; Tue, 20 Jan 2015 21:43:44 +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 66DABFC7 for ; Tue, 20 Jan 2015 21:43:44 +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 4A0561FE023; Tue, 20 Jan 2015 22:43:42 +0100 (CET) Message-ID: <54BECC3F.5050402@selasky.org> Date: Tue, 20 Jan 2015 22:44:31 +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: Uffe Jakobsen , freebsd-usb@freebsd.org Subject: Re: Problem with libusb20_dev_get_port_path() References: <54BD9460.90607@uffe.org> <54BDDB11.3070800@selasky.org> <54BE36AC.9050904@uffe.org> <54BE3FE4.2000206@selasky.org> <54BEB110.4070105@uffe.org> In-Reply-To: <54BEB110.4070105@uffe.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 21:43:44 -0000 On 01/20/15 20:48, Uffe Jakobsen wrote: > > > Hello, > > On 2015-01-20 12:45, Hans Petter Selasky wrote: >> >> It appears there is a minor bug in the kernel regarding this field. See >> below: >> >> https://svnweb.freebsd.org/changeset/base/277417 >> >> Should work now. >> > > Thanks for the quick response and fix > > How far back does the problem reach ? > > Kind regards Uffe Jakobsen > Hi, I think the IOCTL never worked except returning no path (0) like you observed. --HPS