Wolfgang Ocker wrote:
Hi Wolfgang!
On Tue, 2008-08-26 at 20:52 +0200, Wolfgang Denk wrote:
In message 1219774284.3294.52.camel@galileo.recco.de you wrote:
This patch allows a managed switch like the 88E6083 to be directly connected to a 4xx using PHY mode.
It avoids waiting for a link (it's always there) and uses fixed values for speed and duplex mode since both settings are hardware controlled.
How does this patch work in configurations which have such a switch attached to one network interface, but a normal PHY to one or more other interfaces?
It does not work. I guess you have to further increase complexity and handle all the possible configurations (devnum + CONFIG_PHYx_UNMANAGED etc., analogous to the phy address).
In case I interpret the code correctly, different kinds of PHYs on a board are not supported in general.
Thanks, Wolfgang
_
This is a very common situation and was one of the motivations for my effort to move Ethernet initialization to board code. The use of different CONFIGs for each interface is IMHO not scalable. I'm intrigued by the idea of getting specific information from a device tree as has been recently suggested, but wonder if it'll ever happen.
Sorry for the diatribe. I should have the 4xx controller switched over to cpu/board initialization within a couple of days. Let's look then into how to pass PHY specifics to each interface.
regards, Ben