libicsneo/communication
Paul Hollinsky d8798acaa7 Communication: MultiChannel: Properly mask out communication from non-main VNETs
This also makes it possible for Communication to create more instances of Packetizer
This is necessary because Packetizer is not thread safe,
so when we support more VNETs we will need to create more Packetizers.
2020-03-09 13:56:18 -04:00
..
message Implement FlexRay transmit, configuration, and cold start 2019-11-12 20:38:47 -05:00
packet add decoding of transmitted, error, and description fields for CAN packets 2020-02-19 09:36:28 -05:00
communication.cpp Communication: MultiChannel: Properly mask out communication from non-main VNETs 2020-03-09 13:56:18 -04:00
decoder.cpp Begin work on FlexRay support 2019-10-16 16:43:31 -04:00
encoder.cpp Communication: MultiChannel: Properly mask out communication from non-main VNETs 2020-03-09 13:56:18 -04:00
icommunication.cpp Event refactor builds on Windows 2019-06-24 17:59:45 -04:00
multichannelcommunication.cpp Communication: MultiChannel: Properly mask out communication from non-main VNETs 2020-03-09 13:56:18 -04:00
packetizer.cpp Communication: MultiChannel: Properly mask out communication from non-main VNETs 2020-03-09 13:56:18 -04:00