fakeMotor vs fakeMotionControl

[drdanz]

As discussed in #2308 test_motor was renamed as fakeMotor.
Anyway, I realized that fakeMotor and fakeMotionControl seem to be implementing the same thing, but the latter seems more complete.
Is anyone aware of any reason for using fakeMotor instead of fakeMotionControl?
If there aren't reason I propose to deprecate (and eventually remove) the first one.

[drdanz]

The axes parameter of fakeMotor can be replaced with GENERAL::Joints in fakeMotionControl

[drdanz]

Apparently this works almost everywhere, but it does not work for the group device that has a configuration like

device group

[part mymotor]
device fakeMotionControl
axes 10

[part broadcast]
device controlboardwrapper2
subdevice mymotor
name /mymotor

I'm not sure how this is parsed, but adding a [GENERAL] section does not work as expected. I don't know if there is a way to pass the Joint parameter here.

[drdanz]

This seems to work

[part mymotor]
device fakeMotionControl
GENERAL (Joints 10)