I am forwarding Oliver Hartkopp's founded reply
to the list for archival and rest of the RTEMS
community
-- Forwarded Message --
Subject: Re: Request for feedback for CAN message structure
Date: Tuesday 21 of June 2022, 08:55:03
From: Oliver Hartkopp
To: Pavel Pisa , devel
Hello Pavel and Prashanth,
Am 20.06.22 um 22:57 schrieb Pavel Pisa:
Hello Prashanth S and others,
excuse me for lower activity last weeks. We have exams period
and I have lot of other duties and was even ill. I am at Embedded
World in Nuremberg now, so may it be there is some chance to meet
Hello Prashanth S and others,
excuse me for lower activity last weeks. We have exams period
and I have lot of other duties and was even ill. I am at Embedded
World in Nuremberg now, so may it be there is some chance to meet
somebody other from RTEMS community.
As for the e-mail it is better to
IIRC Pavel asked to always being on cc to get CAN related email right to
his inbox instead of email list boxes...
On 6/20/22 18:37, Prashanth S wrote:
Hi All,
This is a request for suggestions and feedback for the CAN message
structure.
*CAN message structure that represents the can
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
