netdev - Re: DSA + Marvell embedded switch question

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20160816181749.GQ14446@lunn.ch>
Date:	Tue, 16 Aug 2016 20:17:49 +0200
From:	Andrew Lunn <andrew@...n.ch>
To:	John Fleming <john@...kefishsolutions.com>
Cc:	netdev@...r.kernel.org
Subject: Re: DSA + Marvell embedded switch question

On Mon, Aug 15, 2016 at 08:17:24PM -0400, John Fleming wrote:
> Hi all, I have a embedded appliance I bought from a vendor and i'm
> being told to file a RFE for this.
> 
> The issue i have is the device has a embedded Marvell switch (88E1514
> ?).

Hi John

1514 is probably a PHY, not a switch. All switches are 88E6XXX.

> LAN1 through LAN6 are part of a single bridge group by default.
> Not sure if that is the correct term because i don't think it was
> created via brctl and doesn't show up in there.
> 
> This is what ethtool shows as the driver. Looks like the driver name
> is marvellmod based on lsmod output.
> 
> ethtool -i LAN1
> driver: marvell switch port
> version: 1.0
> firmware-version:
> bus-info: switch SMI bus
> supports-statistics: no
> supports-test: no
> supports-eeprom-access: no
> supports-register-dump: no
> supports-priv-flags: no
> 
> Also found this
> crw-r--r--    1 root     root      10,   3 Aug 15 17:49 /dev/marvell

These all tell me it is using some proprietary driver, not mainline
Linux code.

> Just wondering if anyone can point me to something that could pull
> this information. I don't have any C know how, but if nudged in the
> right direction i think i could figure it out.

You probably need to contact Marvell and ask them about their
proprietary code. We here don't have access to it.

	    Andrew