netdev - RE: SMSC 8720a/MDIO/PHY help.

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]

Date:	Wed, 13 Apr 2011 23:08:20 -0500
From:	ANDY KENNEDY <ANDY.KENNEDY@...ran.com>
To:	<netdev@...r.kernel.org>
Subject: RE: SMSC 8720a/MDIO/PHY help.

> > -----Original Message-----
> > From: Michael Riesch [mailto:michael@...sch.at]
> > Sent: Wednesday, April 13, 2011 4:19 PM
> > To: netdev@...r.kernel.org
> > Cc: ANDY KENNEDY
> > Subject: Re: SMSC 8720a/MDIO/PHY help.
> >
> >
> > > If you have an idea of something for me to try, I'd love to
> > entertain
> > > it.
> >
> > I am rather new to PHYLIB, but these are my ideas:
> >
> >  1) make sure phy_connect is executed (AFIAK called by MDIO bus
> > driver)

Along this line of though:  phy_connect requires struct net_device, which has a struct net_device_ops within it.  When I do a phy_connect am I supposed to provide the minimal functions for netdev_ops (correct this list if I am mistaken):
ndo_open
ndo_stop
ndo_start_xmit
ndo_get_stats
ndo_set_multicast_list
As well as populate the dev->dev_addr within the struct net_device.

The part that confuses me is that the smsc.c ??driver?? under drivers/net/phy/smsc.c doesn’t do any of this.  This is a phy supported by this file, so should I have to do all this to get the device up?

Spinning,
Andy