mirror of
https://github.com/paparazzi/paparazzi.git
synced 2026-06-06 07:53:43 +08:00
Allen Ibara
2d983a949b
Use "up" and "down" instead of "in" and "out" since the latter are ambiguous depending on which side of the link you believe you are on. Replace -OVERO_LINK_MSG_UNION with OVERO_LINK_MSG_UP and OVERO_LINK_MSG_DOWN This allows the union type to be defined once, instead of repeating the union boilerplate over and over again. Defining the up and down messages independently is useful in the case where two airframes share one message but not the other. One can also use the same message for Up and Down (ala AutopilotMessageFoo for stm_test_spi_link) Change the overo_link union too, replacing the UNION type with the new UP/DOWN types. This way we get type checking on up vs down message type. For example: msg_out = &overo_link.msg_out.uni.up; becomes: msg_up = &overo_link.up.msg;