netdev - How to enable extended Ethtool support for SOCs like the i.mx6

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>] [day] [month] [year] [list]

Date:	Wed, 11 Sep 2013 16:37:29 +0200
From:	Christian Ege <k4230r6@...il.com>
To:	netdev@...r.kernel.org
Subject: How to enable extended Ethtool support for SOCs like the i.mx6

Hello

I am currently developping on a freescale i.mx6 custom design with a
Micrel ksz9031 Phy. Both are supported by Linux. The adjustment of
speed and duplex modes can be done by ethtool without any problems.

Then our hardware department started a request to toggle mdi and mdi-x
modes,this is done through the vendor specific Register 0x1C, of the
PHY. The PHY itself supports this feature. But I can not find any
clear way to add this support in the Kernel.

The ethtool communicates over the freescale fec driver with the PHY.
The FEC Driver itself does not really know what PHY it is attached to.
The only examples about the mdi/mdi-x features in the kernel are
located in the intel drivers which I think do know which PHY
capabilities they can rely on.

What is the preferred way to make this settings available to the user-space?

Is extending the phy_device struct a way to go?

with kind regards,

Christian Ege
--
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