netdev - RE: how to access PHY's registers from user space

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

Date:	Fri, 31 Jul 2015 04:39:18 +0000
From:	Shaohui Xie <Shaohui.Xie@...escale.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: how to access PHY's registers from user space

Sorry!
I have to re-send the email since previous one was rejected due to HTML format.

Best Regards, 
Shaohui Xie

From: Xie Shaohui-B21989 
Sent: Friday, July 31, 2015 12:09 PM
To: netdev@...r.kernel.org; 'David Miller'
Subject: how to access PHY's registers from user space

Hello All,
Is there a general way in user space to access C45 PHY's registers, like dumping some registers?

mii-tool seems obsolete, especially, it cannot support PHYs accessed through Clause 45.

ethtool seems does not support this operation.

PHY lib API phy_mii_ioctl() seems also obsolete, data structure it used is not suitable for C45 PHYs.

/* This structure is used in all SIOCxMIIxxx ioctl calls */
struct mii_ioctl_data {
        __u16           phy_id;
        __u16           reg_num;
        __u16           val_in;
        __u16           val_out;
};   

What should be a proper way to implement accessing PHY's registers in user space? 

To modify the phy_mii_ioctl() to support C45 PHYs? 
Then how about the user space application, should it also be improved?

Or to add sysfs support to a specific PHY's driver if this PHY is interested, 
is this acceptable in upstream?

Welcome to comments!

Best Regards, 
Shaohui Xie

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