From: Stephen Hemminger <shemminger@osdl.org>
To: Ingo Oeser <netdev@axxeo.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] ethtool: flie option to register dump
Date: Mon, 23 Oct 2006 13:06:46 -0700 [thread overview]
Message-ID: <20061023130646.43860b79@freekitty> (raw)
In-Reply-To: <200610241150.19609.netdev@axxeo.de>
On Tue, 24 Oct 2006 11:50:19 +0200
Ingo Oeser <netdev@axxeo.de> wrote:
> Hi Stephen,
>
> Stephen Hemminger schrieb:
> > Add ability to take old raw dumps from a file and decode them.
> > It is kind of limited because you still need to have same device
> > as the raw file, but useful for maintainers to decode raw dumps.
>
> What about putting the (Permanent) MAC into the first 4-6 octets
> of the hexdump and decode+check+warn using this info first
> to avoid mixing up files?
>
> Maybe only the first 4 octets to enhance privacy and still being able
> to detect known "bad" series.
>
> This might prevent user errors when sending such files
> to developers.
>
> Regards
>
> Ingo Oeser
The existing output format for raw is fine for piping into utilities
like hexdump
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-10-25 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 17:46 [PATCH 1/3] ethtool: sky2 GMAC decode Stephen Hemminger
2006-10-18 17:47 ` [PATCH 2/3] ethtool: sky2 more decode Stephen Hemminger
2006-10-18 17:50 ` [PATCH 3/3] ethtool: dump_registers post mortem Stephen Hemminger
2006-10-19 21:53 ` [PATCH] ethtool: more sky2 decode Stephen Hemminger
2006-10-21 18:15 ` [PATCH 3/3] ethtool: dump_registers post mortem Jeff Garzik
2006-10-23 17:51 ` [PATCH 1/3] ethtool: marvell register dump Stephen Hemminger
2006-10-23 17:57 ` [PATCH 2/3] ethtool: flie option to " Stephen Hemminger
2006-10-24 9:50 ` Ingo Oeser
2006-10-23 20:06 ` Stephen Hemminger [this message]
2007-02-09 21:29 ` Jeff Garzik
2006-10-23 17:58 ` [PATCH 3/3] ethtool: allow force hex in " Stephen Hemminger
2006-11-07 9:34 ` [PATCH 1/3] ethtool: marvell " Jeff Garzik
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=20061023130646.43860b79@freekitty \
--to=shemminger@osdl.org \
--cc=jgarzik@pobox.com \
--cc=netdev@axxeo.de \
--cc=netdev@vger.kernel.org \
/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.