From owner-freebsd-usb@freebsd.org  Thu Dec 21 20:14:58 2017
Return-Path: <owner-freebsd-usb@freebsd.org>
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 97A01E87960
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Thu, 21 Dec 2017 20:14:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 8656776591
 for <freebsd-usb@FreeBSD.org>; Thu, 21 Dec 2017 20:14:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBLKEwf5080324
 for <freebsd-usb@FreeBSD.org>; Thu, 21 Dec 2017 20:14:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-usb@FreeBSD.org
Subject: [Bug 224454] Feature request: implement libusb_get_parent and
 libusb_has_capability
Date: Thu, 21 Dec 2017 20:14:58 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: usb
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: hselasky@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-224454-17-lYuy3quThu@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224454-17@https.bugs.freebsd.org/bugzilla/>
References: <bug-224454-17@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 20:14:58 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224454

--- Comment #3 from Hans Petter Selasky <hselasky@FreeBSD.org> ---
Hi,

libusb is the same for -12 and -11. Just make a patch for your current syst=
em
and I'll fix the rest.

> I think libusb_has_capability is easier to implement. Do you think it is =
correct for libusb_has_capability to always return 1 for the hotplug capabi=
lity?

Can you check what is expected by the hotplug capability? What functions mu=
st
be implemented when this capability returns 1?

> I found there is another missing function today:
> libusb_interrupt_event_handler. gvfs uses it in its MTP backend,
> and this is the only libusb function it calls. gvfs has an
> option to disable libusb support, so it doesn't cause build problems.

Is this a variant of the existing "libusb_event_handler_active()"? Can you
investigate a bit?

--HPS

--=20
You are receiving this mail because:
You are the assignee for the bug.=