I'm debugging a fairly awkward system, where the ehernet controller and the phy device connected to the controller's mac are completely independent. (this is in the 2.6.25 tree, btw).
The phy device interface is through SysFs attributes, there is no interrupts, link state is polled by a user space thread. When I try using this new ethernet interface, it's never in the operational 'running' state, so it never gets used. I see that many drivers use netif_carrier_on() to set oper state, but this is invoked from the driver code in the kernel. Is there a recommended way of controlling the interface operstate from user space? Or maybe someone has a suggestion on how to do this in the cleanest possible way? As always, any hints/comments will be highly appreciated, TIA, Vadim _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
