This is a small patch, just to see if I'm doing everything correctly
before starting with bigger stuff.
I've copied the fix from the kernel version and added the description of
timestamps.
Did you use some tool to generate can.txt from LaTeX or SGML ?
Also, what about the man pages available in the same directory as the
LaTeX files ?
Index: kernel/2.6/Documentation/networking/can.txt
===================================================================
--- kernel/2.6/Documentation/networking/can.txt (revision 1197)
+++ kernel/2.6/Documentation/networking/can.txt (working copy)
@@ -25,6 +25,7 @@
4.2 Broadcast Manager protocol sockets (SOCK_DGRAM)
4.3 connected transport protocols (SOCK_SEQPACKET)
4.4 unconnected transport protocols (SOCK_DGRAM)
+ 4.5 Timestamps
5 Socket CAN core module
5.1 can.ko module params
@@ -334,7 +335,7 @@
return 1;
}
- /* paraniod check ... */
+ /* paranoid check ... */
if (nbytes < sizeof(struct can_frame)) {
fprintf(stderr, "read: incomplete CAN frame\n");
return 1;
@@ -475,7 +476,19 @@
4.3 connected transport protocols (SOCK_SEQPACKET)
4.4 unconnected transport protocols (SOCK_DGRAM)
+ 4.5 Timestamps
+
+ For applications in the CAN environment it is often of interest an
+ accurate timestamp of the instant a message from CAN bus has been received.
+ Such a timestamp can be read with ioctl(2) after reading a message from
+ the socket. Example:
+ struct timeval tv;
+ ioctl(s, SIOCGSTAMP, &tv);
+
+ The timestamp on Linux has a resolution of one microsecond and it is set
+ automatically at the reception of a CAN frame.
+
5. Socket CAN core module
-------------------------
--
Daniele Venzano
http://www.brownhat.org
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users
