All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Anil Nair <anilcoll90@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Steven J. Magnani" <steve@digidescorp.com>
Subject: Re: usbview 2.0 release
Date: Wed, 24 Oct 2012 09:41:12 -0700	[thread overview]
Message-ID: <20121024164112.GA2499@kroah.com> (raw)
In-Reply-To: <CAHkwNTnkEANzDe9mUCtrTgE3LLphtr0XENQfC9-J02ygH=-VEA@mail.gmail.com>

On Wed, Oct 24, 2012 at 10:05:48PM +0530, Anil Nair wrote:
> Hello Greg,
> 
> > Look at how the lsusb tool walks the list of all USB devices in the
> > system, using libusb, and port that code over to usbview, replacing the
> > big "walk and parse the devices file" functionality.
> >
> 
> You meant to say replace the functions calling or using debugfs by
> API's of libusb?

Yes.  But note, the debugfs "usage" is just reading a single file and
parsing the structure of that file and filling out an internal "tree" of
USB devices.  So moving that to use libusb should be pretty simple.

> Well i will try working on it, but i can't say a sure time when it
> will be completed..... i know working of USB just need to go through
> libusb API's and some examples.

Again, look at the usbutils source code, it does most of this for you
already, and you can take the code from there since the license is the
same.

good luck,

greg k-h

      reply	other threads:[~2012-10-24 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 16:21 usbview 2.0 release Greg KH
2012-10-22 17:19 ` Anil Nair
2012-10-22 17:37   ` Steven J. Magnani
2012-10-22 17:59     ` Greg KH
2012-10-22 18:31       ` Anil Nair
2012-10-22 18:39         ` Anil Nair
2012-10-22 18:50           ` Greg KH
2012-10-23  4:47             ` Anil Nair
2012-10-24  3:00               ` Greg KH
2012-10-24 16:35                 ` Anil Nair
2012-10-24 16:41                   ` Greg KH [this message]

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=20121024164112.GA2499@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anilcoll90@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=steve@digidescorp.com \
    /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.