All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Neil Kalo <neilkalo@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Steve Holland <sdh4@iastate.edu>,
	Oliver Neukum <oliver@neukum.org>
Subject: Re: usbmc seems broken
Date: Tue, 26 Jan 2010 17:01:25 -0800	[thread overview]
Message-ID: <20100126170125.d199e52c.akpm@linux-foundation.org> (raw)
In-Reply-To: <5c343a41001220840x6ce6bd29q3b69bbc978b1899f@mail.gmail.com>

(cc's added)

On Fri, 22 Jan 2010 16:40:06 +0000
Neil Kalo <neilkalo@gmail.com> wrote:

> I cannot get usbtmc to work with my device. I am using fedora 12:
> 2.6.31.12-174.2.3.fc12.i686.PAE
> 
> Jan 22 15:40:26 localhost kernel: usb 4-1: new full speed USB device
> using ohci_hcd and address 4
> Jan 22 15:40:26 localhost kernel: usb 4-1: New USB device found,
> idVendor=05e6, idProduct=2100
> Jan 22 15:40:26 localhost kernel: usb 4-1: New USB device strings:
> Mfr=2, Product=3, SerialNumber=1
> Jan 22 15:40:26 localhost kernel: usb 4-1: Product: 2100 Multimeter
> Jan 22 15:40:26 localhost kernel: usb 4-1: Manufacturer: KEITHLEY INSTRUMENTS
> Jan 22 15:40:26 localhost kernel: usb 4-1: SerialNumber: 1160791
> Jan 22 15:40:26 localhost kernel: usb 4-1: configuration #1 chosen from 1 choice
> Jan 22 15:40:26 localhost kernel: usbtmc 4-1:1.0: can't read capabilities
> 
> If I compile the original Agilent module from
> "http://www.home.agilent.com/upload/cmc_upload/All/usbtmc.html" It
> works fine:
> 
> Jan 22 15:37:45 localhost kernel: usb 4-1: new full speed USB device
> using ohci_hcd and address 3
> Jan 22 15:37:45 localhost kernel: usb 4-1: New USB device found,
> idVendor=05e6, idProduct=2100
> Jan 22 15:37:45 localhost kernel: usb 4-1: New USB device strings:
> Mfr=2, Product=3, SerialNumber=1
> Jan 22 15:37:45 localhost kernel: usb 4-1: Product: 2100 Multimeter
> Jan 22 15:37:45 localhost kernel: usb 4-1: Manufacturer: KEITHLEY INSTRUMENTS
> Jan 22 15:37:45 localhost kernel: usb 4-1: SerialNumber: 1160791
> Jan 22 15:37:45 localhost kernel: usb 4-1: configuration #1 chosen from 1 choice
> Jan 22 15:37:45 localhost kernel: USBTMC: MKDEV
> Jan 22 15:37:45 localhost kernel: USBTMC: CDEV_ADD f900000 1
> 
> Note that I do get one error line per module load, but this does not
> prevent the device from working in my application:
> Jan 22 15:38:21 localhost kernel: USBTMC: Unable to read data, error -110
> 
> This error also sometimes occurs with the standard kernel module, but
> I never get a functioning connection to my device:
> Jan 16 23:43:36 localhost kernel: usbtmc 1-4.1.1:1.0: can't read capabilities
> Jan 16 23:52:31 localhost kernel: usbtmc 1-4.1.1:1.0: Unable to read
> data, error -110
> 
> Where do I go from here?


  reply	other threads:[~2010-01-27  1:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 16:40 usbmc seems broken Neil Kalo
2010-01-27  1:01 ` Andrew Morton [this message]
2010-01-27  1:59   ` Greg KH
2010-02-04  8:32     ` Neil Kalo
2010-02-24  2:18       ` Greg KH

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=20100126170125.d199e52c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=neilkalo@gmail.com \
    --cc=oliver@neukum.org \
    --cc=sdh4@iastate.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.