The Mesa hostmot2 tree currently carries two Modbus drivers.
The older one lives in src/hal/drivers/mesa-hostmot2/modbus. You write a .mod file describing your device, run modcompile on it, and it generates and compiles a bespoke realtime component from mesa_modbus.c.tmpl for that device. Documented in docs/src/drivers/mesa_modbus.adoc and modcompile(1). The newer one is hm2_modbus, written to replace it. It is a single loadable driver configured with binary MBCCB files built by mesambccc(1), so there is no per-device compile step. Documented in hm2_modbus(9) and mesambccc(1). Keeping both has a concrete cost beyond the duplication. The old driver is the reason hostmot2-serial.h is an exported public header, which constrains work on the hostmot2 headers generally. The only other user is the mesa-pktgyro-test component, which is easy to adjust. So, two questions. To users: is anyone still running a mesa_modbus setup built with modcompile? If so, is there something it does for you that hm2_modbus does not, or is it simply that the configuration has not been migrated? To developers: any objection to deprecating the old driver now, with a note in the docs and a runtime warning, and removing it after a release? If there is a feature gap, I would rather hear it now and see it closed in hm2_modbus than remove something people depend on. -- *Luca Toniolo* _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
