From: Marcel Holtmann <marcel@holtmann.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Patch to add usbmon
Date: Wed, 02 Feb 2005 17:40:17 +0100 [thread overview]
Message-ID: <1107362417.11944.7.camel@pegasus> (raw)
In-Reply-To: <20050201215936.029be631@localhost.localdomain>
Hi Pete,
> > I think if cat is the prefered tool for viewing this file then it should
> > be more human readable. If not, then a binary format should be choosen.
> > Maybe we can implement both. Is this possible?
>
> Yes. Now you know why files were split as they were.
still no reason for me to split things up.
> > > But if you or someone else were to hack on something like usbdump(1),
> > > it would be peachy, I think.
> >
> > I can start with usbdump if we agree on an interface. I personally would
> > prefer a binary interface for that.
>
> If you want to start scoping it, it's fine by me. I was going to concentrate
> on fixing what's needed first, such as getting control setup packets captured
> and things like that.
While I am really thinking about starting usbdump, I may ask why you
have choosen to use debugfs as interface. This will not be available in
normal distribution kernels and I think a general USB monitoring ability
would be great. For example like we have it for Ethernet, Bluetooth and
IrDA. So my idea is to create some /dev/usbmonX (for each bus one) where
usbdump can read its information from. What do you think?
Regards
Marcel
next prev parent reply other threads:[~2005-02-02 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 5:29 Patch to add usbmon Pete Zaitcev
2005-02-01 7:10 ` Greg KH
2005-02-01 8:32 ` Pete Zaitcev
2005-02-01 11:13 ` Marcel Holtmann
2005-02-01 17:55 ` Pete Zaitcev
2005-02-01 21:37 ` Marcel Holtmann
2005-02-02 5:59 ` Pete Zaitcev
2005-02-02 16:40 ` Marcel Holtmann [this message]
2005-02-02 18:54 ` Pete Zaitcev
2005-02-05 0:19 ` Marcel Holtmann
2005-02-02 6:25 ` Pete Zaitcev
2005-02-04 23:47 ` 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=1107362417.11944.7.camel@pegasus \
--to=marcel@holtmann.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox