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: Tue, 23 Oct 2012 20:00:02 -0700	[thread overview]
Message-ID: <20121024030002.GB7982@kroah.com> (raw)
In-Reply-To: <CAHkwNTmqVkjnZBi01RkY3McSOHYFOvb4m82Lfrc_dVSxSoBWDg@mail.gmail.com>

On Tue, Oct 23, 2012 at 10:17:22AM +0530, Anil Nair wrote:
> Hello Greg,
> 
> > No, debugfs needs to be mounted at /sys/kernel/debug/  Is it not mounted
> > that way for you?  Perhaps it is mounted with root-only access (default
> > for 3.7-rc1 and newer kernels)?
> 
> Yes you are right i verified "/sys/kernel/debug" has root-only access.
> The kernel version i am using is 3.0.0-26-generic(Default kernel
> provided by ubuntu 11.10 amd64).
> 
> > I should just port the thing to use libusb instead of debugfs, but
> > that's a larger job for such a low-priority tool.
> 
> If you don't mind i would like to give it a try, though most of the
> terminologies i don't know but i would like to give it a try, just
> guide me on way of doing it thats all.

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.

It shouldn't be that hard, if you run into any problems, please let me
know.

thanks,

greg k-h

  reply	other threads:[~2012-10-24  2:59 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 [this message]
2012-10-24 16:35                 ` Anil Nair
2012-10-24 16:41                   ` 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=20121024030002.GB7982@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.