Feature eth v9

[pkazanzides]

Changes for Ethernet-only network (FPGA V3), with option to force use of Ethernet/Firewire bridge.

[adeguet1]

I'm fine with the naming choice, i.e. fw, udp, udpfw, eth, ethfw. The main issue is the change of meaning for 'udp' breaking backward compatibility. There are not many groups actively using udp so changing its meaning won't be too disruptive. But it might still be a bit confusing for v2 users. Let's say I'm using a single arm and connecting with ethernet. It would make sense to use udp since it's not obvious there's a fw bus in the v2 controller. Maybe we can create udpfw, udpudp and fwfw while deprecating udp and fw None of these are pretty though.

[pkazanzides]

Yes, I thought about this for some time. My conclusion was that "udp" (or "eth") means to use the default (or best) setup for the given hardware, which would be a backward-compatible view. For FPGA V2, it always means using the Ethernet/Firewire bridge (i.e., same as "udpfw" or "ethfw"). Another way to look at this is that "udpfw" and "ethfw" are only relevant for FPGA V3, in which case there is no backward compatibility issue. Maybe it wasn't obvious in the code that the software would still use Firewire if you specify "udp" on a V2 system.