Request for feedback for CAN message structure

[Prashanth S]

Hi All,

This is a request for suggestions and feedback for the CAN message
structure.

*CAN message structure that represents the can messages from application to
driver:*

struct can_message {
uint32_t timestamp;
uint32_t id;                 // 32 bits to support extended id (29 bits)
uint16_t flags;            // RTR | BRS | EXT ...
uint8_t dlc;                 // (0 - 8) | 12 | 16 | 20 | 24 | 32 | 48 | 64
uint8_t res;                 // reserved for alignment.
uint8_t data[64];         // For supporting data transfer up to 64 bytes.
};

This is the CAN messages structure created based on the suggestions in the
mail chain and looking through other CAN solutions (Nuttx, GRCAN, LinCAN).

Regards
Prashanth S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20220620/96b5615a/attachment.htm>