From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 62B91138247 for ; Sat, 9 Nov 2013 12:30:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 925D8E09B0; Sat, 9 Nov 2013 12:30:18 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E21FFE0949 for ; Sat, 9 Nov 2013 12:30:17 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vf7g1-0005PF-U2 for gentoo-amd64@lists.gentoo.org; Sat, 09 Nov 2013 13:30:09 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Nov 2013 13:30:09 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Nov 2013 13:30:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb Date: Sat, 9 Nov 2013 12:29:49 +0000 (UTC) Message-ID: References: <20131108222553.33af27243ad5aa2411c3f0ff@comcast.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT 6e6fd84 /usr/src/portage/src/egit-src/pan2) X-Archives-Salt: 6ba176cd-d4d1-478c-bce0-bae72a6b180b X-Archives-Hash: f4203beb18855ae03d70a7202fb518d2 Frank Peters posted on Fri, 08 Nov 2013 22:25:53 -0500 as excerpted: > The utility usb-devices, which uses libusb, can produce data on the > scanner, but lsusb, which also uses libusb but depends on usbfs, fails. > > Does anyone know to resolve such a problem? How can I get my scanner to > be utilized by libusb and sane? I haven't had a scanner in awhile, but based on what I've read verified by what I see for other usb devices, udev creates usb devices in /dev/bus/usb. Each usb port is a (three-digit sequentially numbered) directory, with the individual device functions on that port appearing as (again three-digit sequentially numbered) device nodes. Usually there'll only be one such function per dir, but some devices, such as my Logitech USB mouse/keyboard, have two or more. There's also /sys/bus/usb/, which like most /sys/ dirs, contains trees with information, in this case about usb devices. I believe that's all kernel level, however, with udev in fact using some of the information found there to populate its udev device tree. Libusb, meanwhile, has been updated to work with the /dev/bus/usb/ tree, so AFAIK that's what you need to create... somehow. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman