Hello,
here is another patch, it adds the BCM introduction and a tentative
subdivision in sections for everything else. I hope editing it with vim
is the same :-)
For now I decided to keep everything in a single file.
Thsnk, bye
Index: kernel/2.6/Documentation/networking/can.txt
===================================================================
--- kernel/2.6/Documentation/networking/can.txt (revision 1198)
+++ kernel/2.6/Documentation/networking/can.txt (working copy)
@@ -23,6 +23,15 @@
4.1.3 RAW socket option CAN_RAW_LOOPBACK
4.1.4 RAW socket option CAN_RAW_RECV_OWN_MSGS
4.2 Broadcast Manager protocol sockets (SOCK_DGRAM)
+ 4.2.1 Opening BCM sockets
+ 4.2.2 BCM messages (struct bcm_msg_head)
+ 4.2.3 TX_SETUP opcode
+ 4.2.4 TX_DELETE opcode
+ 4.2.5 TX_READ opcode
+ 4.2.6 TX_SEND opcode
+ 4.2.7 RX_SETUP opcode
+ 4.2.8 RX_DELETE opcode
+ 4.2.9 RX_READ opcode
4.3 connected transport protocols (SOCK_SEQPACKET)
4.4 unconnected transport protocols (SOCK_DGRAM)
4.5 Timestamps
@@ -473,6 +482,41 @@
&recv_own_msgs, sizeof(recv_own_msgs));
4.2 Broadcast Manager protocol sockets (SOCK_DGRAM)
+
+ The Broadcast Manager (BCM) provides functions to send CAN frames
+ once or periodically, as well as notify applications of changes in
+ received CAN frames, recognizing specific CAN IDs.
+
+ Capabilities on the trasmission side:
+ - Cyclic transmission of a CAN frame with a given interval
+ - Modification of message content and intervals at runtime (e.g.
+ switching to a new interval with or without immediate restart of
+ the timer)
+ - Automatically switching to a second interval after a certain number
+ of frames has been sent
+ - Instant transmission of changed frames, without influencing the
+ interval cycle
+ - One-time transmission of CAN messages
+
+ Capabilities on the receiving side:
+ - Receive filter to detect changes in frame ID, data or length (DLC)
+ - Receive filter for multiplex frames (e.g. with packet counters in
+ the data field)
+ - RTR replies to messages
+ - Time-out monitoring of frames
+ - Frequency reduction of messages (throttle function) to the user
+ application
+
+ 4.2.1 Opening BCM sockets
+ 4.2.2 BCM messages (struct bcm_msg_head)
+ 4.2.3 TX_SETUP opcode
+ 4.2.4 TX_DELETE opcode
+ 4.2.5 TX_READ opcode
+ 4.2.6 TX_SEND opcode
+ 4.2.7 RX_SETUP opcode
+ 4.2.8 RX_DELETE opcode
+ 4.2.9 RX_READ opcode
+
4.3 connected transport protocols (SOCK_SEQPACKET)
4.4 unconnected transport protocols (SOCK_DGRAM)
--
Daniele Venzano
http://www.brownhat.org
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users
