public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marcel Janssen <korgull@home.nl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oliver@neukum.org>,
	USB list <linux-usb@vger.kernel.org>,
	Stefan Kopp <stefan_kopp@agilent.com>,
	Felipe Balbi <me@felipebalbi.com>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: add USB test and measurement class driver - round 2
Date: Thu, 28 Aug 2008 13:38:44 -0700	[thread overview]
Message-ID: <20080828203844.GC20537@kroah.com> (raw)
In-Reply-To: <200808281858.42486.korgull@home.nl>

On Thu, Aug 28, 2008 at 06:58:41PM +0200, Marcel Janssen wrote:
> On Thursday 28 August 2008 01:47:20 Greg KH wrote:
> > Great, all done now.
> >
> > Here's the updated version.
> 
> I've just installed this version.
> 
> Here's what I see so far :
> 
> The driver inserts well and when I connect my device it shows /dev/usbtmc0 
> with major 180 and minor 176.
> It only creates one device (Stefan's driver created two) but I'm not sure if 
> that has changed for a reason so just let you know.

Yes, the old driver had a "control and debug " channel at minor 0, which
isn't needed anymore.

> When I disconnect my device, usbtmc0 will not be destroyed. After connecting 
> the device a couple of times I have a lot of /dev/usbtmc.. files.

Hm, that's not good, something's wrong here.

Can you enable CONFIG_USB_DEBUG and rebuild the driver and send me the
kernel log messages when you plug the device in and then remove it?

> I would expect the following to work :
> echo :*IDN?>/dev/usbtmc0
> But it returns : No such device

Yeah, I would expect that to work as well.  The debug information might
be helpful here also.

> Using echo and cat to test the device is quite convenient, but is this 
> supposed to work yet ?

Yes it should.

> I checked /sys a bit and found that the endpoints are correctly found.    

Good, how about the capability information?  That should be in sysfs as
well, does that show the proper values?

thanks,

greg k-h

  reply	other threads:[~2008-08-28 22:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 17:20 [PATCH] USB: add USB test and measurement class driver - round 2 Greg KH
2008-08-27 18:28 ` Alan Stern
2008-08-27 18:36   ` Greg KH
2008-08-27 18:58     ` Alan Stern
2008-08-27 19:05       ` Oliver Neukum
2008-08-27 19:16         ` Alan Stern
2008-08-27 23:48           ` Greg KH
2008-08-27 23:47       ` Greg KH
2008-08-28 10:10         ` Oliver Neukum
2008-08-28 16:17           ` Greg KH
2008-08-28 21:29             ` Oliver Neukum
2008-08-28 16:58         ` Marcel Janssen
2008-08-28 20:38           ` Greg KH [this message]
2008-08-29  6:57           ` stefan_kopp
2008-08-29  7:46             ` Oliver Neukum
2008-08-29  8:14               ` stefan_kopp
2008-08-29  8:34                 ` Oliver Neukum
2008-08-29  9:13                   ` stefan_kopp
2008-08-29 11:33                     ` Oliver Neukum
2008-08-29 14:39             ` Greg KH
2008-08-29 16:41               ` Marcel Janssen
2008-08-29 20:01                 ` Greg KH
2008-08-27 18:37   ` Oliver Neukum

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=20080828203844.GC20537@kroah.com \
    --to=greg@kroah.com \
    --cc=korgull@home.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --cc=oliver@neukum.org \
    --cc=stefan_kopp@agilent.com \
    --cc=stern@rowland.harvard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox