On 09/20/2010 04:28 PM, [email protected] wrote: > Hello all, > > we are doing some CANopen stuff with SocketCAN again and I have > some questions / feature requests here.
... > So, to sum that much stuff up: > > A) The proposal to extend CAN message with self reception flag. The > self-received messages will have that flag set. One of the 4 unused > bits of the can_frame.can_dlc may be e.g. used for that. That's feasible but for backward compatibility we should not use the member can_dlc. I would prefer to use the padding bytes between can_dlc and the data bytes of struct can_frame: http://lxr.linux.no/#linux+v2.6.35.5/include/linux/can.h#L57 > B) Is it possible to label CAN packets in the similar way as done by > "--set-mark" in iptables? Hm, how should the label be sent over the CAN bus? Or should it be used just for the loopbacked messages only? What would be the advantages vs. A)? It's possible of course, but it would require much more code as A) and an interface to handle it. > C) The looping back of self reception messages shall be done in CAN > Tx interrupt and not in the ".ndo_start_xmit" . That's already the case for most CAN controllers (if IFF_ECHO is supported). > D) Do we still need extra ioctl call to get the Rx message timestamp? > I remember the discussion about the possibility to pass timestamp > with the message itself about two years ago. Have a look to the candump.c file of the CAN utils. Wolfgang. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
