On 12.02.2024 16:14:04, Oliver Hartkopp wrote: > CAN XL data frames contain an 8-bit virtual CAN network identifier (VCID). > A VCID value of zero represents an 'untagged' CAN XL frame. > > To receive and send these optional VCIDs via CAN_RAW sockets a new socket > option CAN_RAW_XL_VCID_OPTS is introduced to define/access VCID content: > > - tx: set the outgoing VCID value by the kernel (one fixed 8-bit value) > - tx: pass through VCID values from the user space (e.g. for traffic replay) > - rx: apply VCID receive filter (value/mask) to be passed to the user space > > With the 'tx pass through' option CAN_RAW_XL_VCID_TX_PASS all valid VCID > values can be sent, e.g. to replay full qualified CAN XL traffic. > > The VCID value provided for the CAN_RAW_XL_VCID_TX_SET option will > override the VCID value in the struct canxl_frame.prio defined for > CAN_RAW_XL_VCID_TX_PASS when both flags are set. > > With a rx_vcid_mask of zero all possible VCID values (0x00 - 0xFF) are passed > to the user space when the CAN_RAW_XL_VCID_RX_FILTER flag is set. Without this > flag only untagged CAN XL frames (VCID = 0x00, CANXL_VCID flag unset) are > delivered to the user space. > > The 8-bit VCID is stored inside the CAN XL prio element (only in CAN XL > frames!) to not interfere with other CAN content or the CAN filters > provided by the CAN_RAW sockets and kernel infrastruture. > > Signed-off-by: Oliver Hartkopp <socketcan@xxxxxxxxxxxx> What does that mean for https://lore.kernel.org/all/20240128183758.68401-1-socketcan@xxxxxxxxxxxx/ Marc -- Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung Nürnberg | Phone: +49-5121-206917-129 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Attachment:
signature.asc
Description: PGP signature
