joysticks: Add the Thrustmaster SimTask FarmStick flight joystick

[rafaellehmkuhl]

Based on some information provided by a user (Geoffrey) in our forums and by email exchanges.

productName: SimTask FarmStick Right
vendorId:    0x044F (1103) ThrustMaster, Inc.
productId:   0x0416 (1046)
opened:      true
collections[0]
  Usage: 0001:0004 (Generic Desktop > Joystick)
  Input reports: 0x01
  Feature reports: 0xF3, 0xF1, 0xF2
Input report 0x01
  33 values * 1 bit (bits 0 to 32)
    Data,Var,Abs
    Usages: 0009:0001 (Button Button 1) to 0009:0021 (Button Button 33)
    Logical bounds: 0 to 1
  7 values * 1 bit (bits 33 to 39)
    Cnst,Var,Abs
    Logical bounds: 0 to 1
  3 values * 16 bits (bits 40 to 87)
    Data,Var,Abs
    Usages:
      0001:0030 (Generic Desktop > X)
      0001:0031 (Generic Desktop > Y)
      0001:0032 (Generic Desktop > Z)
    Logical bounds: 0 to 65535
  5 values * 8 bits (bits 88 to 127)
    Data,Var,Abs
    Usages:
      0001:0033 (Generic Desktop > Rx)
      0001:0034 (Generic Desktop > Ry)
      0001:0035 (Generic Desktop > Rz)
      0001:0036 (Generic Desktop > Slider)
      0001:0037 (Generic Desktop > Dial)
    Logical bounds: 0 to 255
  47 values * 8 bits (bits 128 to 503)
    Cnst,Var,Abs
    Usage: 0001:0050 (Generic Desktop usage 0x0050)
    Logical bounds: 0 to 255
Feature report 0xF3
  63 values * 8 bits (bits 0 to 503)
    Data,Var,Abs
    Usage: 0001:0048 (Generic Desktop > Resolution Multiplier)
    Logical bounds: 0 to 255
Feature report 0xF1
  63 values * 8 bits (bits 0 to 503)
    Data,Var,Abs
    Usage: 0001:0047 (Generic Desktop > Feature Notification)
    Logical bounds: 0 to 255
Feature report 0xF2
  63 values * 8 bits (bits 0 to 503)
    Data,Var,Abs
    Usage: 0001:0047 (Generic Desktop > Feature Notification)
    Logical bounds: 0 to 255

Relevant to #2128

[ArturoManzoli]

Nice diagram! It has all the necessary bindings for a default profile.

Can we make a predefined axes and inputs function mappings, so when the user connects one of these or some others known devices, the profile will be auto loaded?

[rafaellehmkuhl]

Nice diagram! It has all the necessary bindings for a default profile.

Can we make a predefined axes and inputs function mappings, so when the user connects one of these or some others known devices, the profile will be auto loaded?

We can, but we have to discuss about a default pattern with the Support and R&D team, so better to do it in a separated PR.

This one is necessary for the user to have his joystick recognized and its mapping be separated from other unknown controllers.

[ArturoManzoli]

Nice diagram! It has all the necessary bindings for a default profile.
Can we make a predefined axes and inputs function mappings, so when the user connects one of these or some others known devices, the profile will be auto loaded?

We can, but we have to discuss about a default pattern with the Support and R&D team, so better to do it in a separated PR.

This one is necessary for the user to have his joystick recognized and its mapping be separated from other unknown controllers.

Agreed, it has to be done on a separate PR. I'll open an issue so we keep track of the task.

I think this will open nice possibilities for different joysticks and cockpit use cases