linux-kernel - Re: [PATCH] Add Broadcom PHY support

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: <1165298581.29784.58.camel@localhost.localdomain>
Date:	Tue, 05 Dec 2006 17:03:01 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Amy Fong <amy.fong@...driver.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	jeff@...zik.org
Subject: Re: [PATCH] Add Broadcom PHY support

> I believe that this fiber enabling can be done by defining config_init in the phy_driver struct.
> 
> struct phy_driver {
> <snip>
>         /* Called to initialize the PHY,
> 	 * including after a reset */
> 	int (*config_init)(struct phy_device *phydev);
> <snip>
> };

Well... I don't know for sure... thing is, enabling the fiber mode is a
rather platform specific thing. So it's the MAC driver that knows wether
it wants it on a PHY and should call into the driver.

It's difficult to abstract all possible PHY config options tho... some
MACs might want to enable low power, some don't because they have issues
with it, that sort of thing, though.

Not sure what the best solution is at this point... Maybe an ascii
string to pass the PHY driver is the most flexible, though a bit yucky,
or we try to have a list of all the possible configuration options in
phy.h and people just add new ones that they need as they add support
for them...

Sounds grossly like an in-kernel ioctl tho...

Ben.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/