netdev - Re: HW communication debugging interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151005145542.GJ2278@nanopsycho.orion>
Date:	Mon, 5 Oct 2015 16:55:42 +0200
From:	Jiri Pirko <jiri@...nulli.us>
To:	Andrew Lunn <andrew@...n.ch>
Cc:	"Rosen, Rami" <rami.rosen@...el.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"eladr@...lanox.com" <eladr@...lanox.com>,
	"idosch@...lanox.com" <idosch@...lanox.com>
Subject: Re: HW communication debugging interface - ideas?

Mon, Oct 05, 2015 at 04:49:41PM CEST, andrew@...n.ch wrote:
>> >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?

Yep, but that does not really matter. I believe we should find debugging
interface which is protocol agnostic. Just arbitrary messages
monitoring.


>
>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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html