From: Andrew Lunn <andrew@lunn.ch>
To: Jiri Pirko <jiri@resnulli.us>
Cc: "Rosen, Rami" <rami.rosen@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"eladr@mellanox.com" <eladr@mellanox.com>,
"idosch@mellanox.com" <idosch@mellanox.com>
Subject: Re: HW communication debugging interface - ideas?
Date: Mon, 5 Oct 2015 16:49:41 +0200 [thread overview]
Message-ID: <20151005144941.GC8673@lunn.ch> (raw)
In-Reply-To: <20151005095633.GE2278@nanopsycho.orion>
> >Are you referring here to messages of the EMAD protocol ?
I know nothing about this protocol.....
Does it at least use standard Ethernet framing? Source and Destination
header and an EtherType which mean EMAD?
Marvell has a way to access registers of their switches using Ethernet
Frames, and they are valid frames with a specific EtherType. Linux
does not use them, but if it did, i would of thought passing them
along using the normal pcap interface would be trivial.
Andrew
next prev parent reply other threads:[~2015-10-05 14:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:51 HW communication debugging interface - ideas? Jiri Pirko
2015-10-05 8:54 ` Jiri Pirko
2015-10-05 9:38 ` David Miller
2015-10-05 9:45 ` Jiri Pirko
2015-10-05 9:54 ` Rosen, Rami
2015-10-05 9:56 ` Jiri Pirko
2015-10-05 14:49 ` Andrew Lunn [this message]
2015-10-05 14:55 ` Jiri Pirko
2015-10-05 14:58 ` Andrew Lunn
2015-10-05 15:18 ` Jiri Pirko
2015-10-05 15:29 ` John Fastabend
2015-10-05 15:35 ` Jiri Pirko
2015-10-05 15:47 ` John Fastabend
2015-10-06 8:14 ` Jiri Pirko
2015-10-06 14:54 ` John Fastabend
2015-10-06 15:02 ` Jiri Pirko
2015-10-06 15:02 ` Andrew Lunn
2015-11-01 17:58 ` Guy Harris
2015-10-05 12:28 ` Thomas Graf
2015-10-05 18:32 ` Marcelo Ricardo Leitner
2015-10-05 20:40 ` Jiri Pirko
2015-11-01 16:51 ` David Miller
2015-11-02 6:13 ` Jiri Pirko
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=20151005144941.GC8673@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=rami.rosen@intel.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.