From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Tomasz Moń" <desowin@gmail.com>,
linux-usb@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
zaitcev@redhat.com
Subject: Re: [PATCH] usbmon: Report device address assigned to USB device
Date: Tue, 14 Jan 2020 15:06:47 -0600 [thread overview]
Message-ID: <20200114150605.6e5f07cd@suzdal.zaitcev.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2001131003350.1502-100000@iolanthe.rowland.org>
On Mon, 13 Jan 2020 10:05:42 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:
> > Alan's suggestion of leaving the physical address in /sys appeals
> > the most to me, honestly. One thing though, libpcap will need to
> > rifle through /sys and then store that address, so its serialization
> > has to be changed no matter what. Unfortunately, I'm wholly ignorant
> > as to what syntax it uses and how extensible it is.
>
> Alternatively, libpcap can ignore the issue and just display the device
> numbers, as it does now. A separate program or the user could convert
> the number to a physical address, if necessary, using the information
> in sysfs.
I thoght that people sometimes saved the traces and replayed them
on other machines, which obviously have their own /sys or even run
Windows or iOS.
-- Pete
prev parent reply other threads:[~2020-01-14 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 9:37 [PATCH] usbmon: Report device address assigned to USB device Tomasz Moń
2020-01-06 23:09 ` Pete Zaitcev
2020-01-08 15:55 ` Greg Kroah-Hartman
2020-01-11 23:52 ` Pete Zaitcev
2020-01-13 15:05 ` Alan Stern
2020-01-14 21:06 ` Pete Zaitcev [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=20200114150605.6e5f07cd@suzdal.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=corbet@lwn.net \
--cc=desowin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--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