public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb
Date: Sat, 9 Nov 2013 12:29:49 +0000 (UTC)	[thread overview]
Message-ID: <pan$4ef9f$38432b1f$1fec27b3$76672b85@cox.net> (raw)
In-Reply-To: 20131108222553.33af27243ad5aa2411c3f0ff@comcast.net

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



  reply	other threads:[~2013-11-09 12:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  3:25 [gentoo-amd64] USB Scanner Problems with Newer Kernels/Libusb Frank Peters
2013-11-09 12:29 ` Duncan [this message]
2013-11-09 16:45   ` [gentoo-amd64] " Frank Peters
2013-11-09 20:40     ` Barry Schwartz
2013-11-09 21:38       ` Frank Peters
2013-11-09 22:11         ` Barry Schwartz
2013-11-09 22:57           ` Mark Knecht
2013-11-09 23:10             ` Barry Schwartz
2013-11-10 16:54               ` Tanstaafl
2013-11-10 17:08                 ` Barry Schwartz
2013-11-09 23:25             ` Frank Peters
2013-11-09 23:57               ` Barry Schwartz
2013-11-10  1:30   ` [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb [Solved] Frank Peters
2013-11-10  1:53     ` Barry Schwartz
2013-11-10  2:36       ` Frank Peters
2013-11-10  4:26       ` Frank Peters
2013-11-12  0:03       ` Frank Peters
2013-11-12 23:18         ` [gentoo-amd64] " Jörg Schaible
2013-11-13  9:14           ` Paul Jewell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$4ef9f$38432b1f$1fec27b3$76672b85@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox