Re: Binding FCC interfaces to device names in reverse order

quoted

Does anyone know why changing the device ids breaks the fs_enet driver ?

Obviously, because board-specific platform_data fixup use that id field to
detect what soc device is that - fcc1 or fcc2 this case. So the phy's will
be wrong-assigned, as well as other stuff.

To change order pdevs are registered, you may try to disable all the fccs
at the startup, and then enable them after ppc_sys_init, or just shoot
enable-disable seq (this was't tested at all, but supposed to work).

Enabling the FCCs in a device_initcall() call instead of arch_initcall() 
works. I had to call ppc_sys_device_fixup manually.

Thanks for your help.

Laurent Pinchart