public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: root@mauve.demon.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB userspace tools.
Date: Sun, 31 Aug 2003 10:28:12 -0700	[thread overview]
Message-ID: <20030831172812.GA20548@kroah.com> (raw)
In-Reply-To: <200308311244.NAA19278@mauve.demon.co.uk>

On Sun, Aug 31, 2003 at 01:44:17PM +0100, root@mauve.demon.co.uk wrote:
> Is there a tool for accessing USB devices, without actually writing
> a driver? Or perhaps more accurately a driver in scriptorspace.
> Perhaps something that exports a number of named pipes that correspond
> to endpoints?

Look at libusb which uses usbfs to do that from userspace without
writing a kernel driver.

Good luck,

greg k-h

  reply	other threads:[~2003-08-31 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 11:59 USB not working correctly in 2.6.0-test4-mm4 Petr Baudis
2003-08-31 12:44 ` USB userspace tools root
2003-08-31 17:28   ` Greg KH [this message]
2003-08-31 14:17 ` USB not working correctly in 2.6.0-test4-mm4 Petr Baudis
2003-08-31 17:30 ` 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=20030831172812.GA20548@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@mauve.demon.co.uk \
    /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