Lines Matching full:address

35   not necessarily know its source address. Although, at least one process per
36   ECU should know the source address. Other processes should be able to reuse
37   that address. This way, address parameters for different processes
42 * **Dynamic addressing:** Address Claiming in J1939 is time critical.
43   Furthermore, data transport should be handled properly during the address
63 cannot share ECU addresses. A single ECU (or virtual ECU) address is used by
85 Destination Address, which is _not_ part of the PGN. When communicating a PGN
87 of the PGN shall be set to zero. The Destination Address shall be set
90 Regarding PGN mapping to 29-bit CAN identifier, the Destination Address shall
103 For dynamic addressing, so-called Address Claiming, extra support is foreseen
105 a successful address claim, the kernel keeps track of both NAME and source
106 address being claimed. This serves as a base for filter schemes. By default,
109 Mixed mode packets (from a static to a dynamic address or vice versa) are
111 local & remote address and are applicable for J1939 sockets.
154 local address to a socket.
190 ``can_addr.j1939.addr`` contains the address.
192 The ``bind(2)`` system call assigns the local address, i.e. the source address when
196 of the incoming packet. The NAME filter will work only if appropriate Address
200 On the other hand ``connect(2)`` assigns the remote address, i.e. the destination
201 address. The PGN from ``connect(2)`` is used as the default PGN when sending
206 Both ``write(2)`` and ``send(2)`` will send a packet with local address from ``bind(2)`` and the
207 remote address from ``connect(2)``. Use ``sendto(2)`` to overwrite the destination
208 address.
279 Destination Address, name and packet priority (if applicable) are attached to
306 Distinction has to be made between using the claimed address and doing an
307 address claim. To use an already claimed address, one has to fill in the
308 ``j1939.name`` member and provide it to ``bind(2)``. If the name had claimed an address
309 earlier, all further messages being sent will use that address. And the
312 An exception on this is PGN 0x0ee00. This is the "Address Claim/Cannot Claim
313 Address" message and the kernel will use the ``j1939.addr`` member for that PGN if
316 To claim an address following code example can be used:
332 	/* for Address Claiming broadcast must be allowed */
336 	/* configured advanced RX filter with PGN needed for Address Claiming */
367 If no-one else contests the address claim within 250ms after transmission, the
372 If another ECU claims the address, the kernel will mark the NAME-SA expired.
373 No socket bound to the NAME can send packets (other than address claims). To
374 claim another address, some socket bound to NAME, must ``bind(2)`` again, but with
375 only ``j1939.addr`` changed to the new SA, and must then send a valid address claim
380 default Address Claiming daemon.