netdev - fixed phy -- how do we decide to use this code?

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

Message-Id: <B660E2DF-5F6A-4939-9D20-3AB8E7C69EDB@kernel.crashing.org>
Date:	Wed, 15 Apr 2009 10:54:40 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Vitaly Bordug <vitb@...nel.crashing.org>,
	Anton Vorontsov <avorontsov@...mvista.com>
Cc:	Linuxppc-dev Development <linuxppc-dev@...abs.org>,
	netdev@...r.kernel.org
Subject: fixed phy -- how do we decide to use this code?

Vitaly, Anton

You guys have used this code.. I was wondering how we decide to used  
the fixed phy vs another phy.  Is this a runtime decision based on  
something in the device tree or purely at compile time?

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