Who is working on CAN FD for AUTOSAR

Hello,

can4linux already defines in the length field in the CAN message structure as

short      int  length;  /**< number of bytes in the CAN message */

The most engineers I asked like to have the number of bytes in the CAN API
instead of the data length code (DLC)

When a CAN frame should be transmitted, the user has to specify the real number of bytes
in this canmsg_t struct. The driver then will convert it to a valid DLC
which will carry the number of bytes requested.
An still open question is, if the driver should fill the unused bytes up to the next possible frame length with patterns that don't cause stuff bit insertion.

The receiving side will get the number of bytes in the received frame instead of the DLC.
This length information is of 0...8, 12, 16, 20, 24, 32, 48, 64.
And of course, the receiver has to know what it is receiving and how many bytes in the frame
are really used.

How will AUTOSAR handle the DLC with CAN FD controllers in the "Specification of CAN Driver"?
I would be glad hearing from you what you are going to standardize. 

-- 
mit freundlichen Grüßen
       Heinz-Jürgen Oertel
       emtas GmbH

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAABAgAGBQJSwBziAAoJENViPQy9fcm7IK0H/2MVR/Bji8OVVlNlXI1AZnjj
IqMC5f/KroewGeWFQ8px3fghL7ei0hTYPC3QIxJpZP0t5PDNWjILZPScp2DbvR1S
nwzWnqnlSbb7EkXSNOeZavd6BitjJm7MYPC2W0edpg0ams6dDuuYL8wgHoGKMxXc
B8V008FmfiBqE2DdYybHL3Jx46MgUsGpX7zaNh7RTBcodPbvia/9Zn+x1t7yMa1r
XwK8LjrQPk+ztO9vB7nT2aPhmCX4iXYHyj9jFQ1CK2OvmmtM6Op+wH8ZONSEhWc4
wCDWsH/Aln8PGTjq9ehMvdHvKLs2Rpc/bp6MMy9gWHN6LdIaX61X60CBASu6R4s=
=kXYd
-----END PGP SIGNATURE-----