-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-37085: Expose SocketCAN bcm_msg_head flags #13646
bpo-37085: Expose SocketCAN bcm_msg_head flags #13646
Commits on Jun 18, 2019
-
bpo-37085: Expose SocketCAN bcm_msg_head flags
Expose the CAN_BCM SocketCAN constants used in the bcm_msg_head struct flags (provided by <linux/can/bcm.h>) under the socket library. This adds the following constants with a CAN_BCM prefix: * SETTIMER * STARTTIMER * TX_COUNTEVT * TX_ANNOUNCE * TX_CP_CAN_ID * RX_FILTER_ID * RX_CHECK_DLC * RX_NO_AUTOTIMER * RX_ANNOUNCE_RESUME * TX_RESET_MULTI_IDX * RX_RTR_FRAME * CAN_FD_FRAME
Configuration menu - View commit details
-
Copy full SHA for 6d1d880 - Browse repository at this point
Copy the full SHA 6d1d880View commit details
Commits on Jul 23, 2019
-
bpo-37085: Only use #ifdef for CAN_FD_FRAME
The CAN_FD_FRAME flag was introduced in the 4.8 kernel, while the other ones were present since SocketCAN drivers were mainlined in 2.6.25. As such, it is probably unnecessary to guard against these constants being missing.
Configuration menu - View commit details
-
Copy full SHA for 604bea9 - Browse repository at this point
Copy the full SHA 604bea9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e0b9c7 - Browse repository at this point
Copy the full SHA 9e0b9c7View commit details -
Add note in docs about CAN_BCM_CAN_FD_FRAME
The CAN_BCM_CAN_FD_FRAME constant mirrors the availability in the Linux kernel. This constant was introduced in Linux 4.8 kernels.
Configuration menu - View commit details
-
Copy full SHA for 28662f1 - Browse repository at this point
Copy the full SHA 28662f1View commit details -
bpo-37085: Use support.requires_linux_version
Use support.requires_linux_version to guard BCM flag CAN_FD_FRAME, which is only present on Linux >= 4.8.
Configuration menu - View commit details
-
Copy full SHA for b969e22 - Browse repository at this point
Copy the full SHA b969e22View commit details
Commits on Jul 25, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 128c1c1 - Browse repository at this point
Copy the full SHA 128c1c1View commit details
Commits on Jul 29, 2019
-
bpo-37085: Remove test for CAN_BCM_CAN_FD_FRAME
This constant doesn't exist on Ubuntu 16.04 LTS, since linux-libc-dev ships 4.4.x headers from the repos, while the feature was added in the 4.8.x kernel series. However, Ubuntu 16.04 supports the 4.15.x kernel series, but since linux-libc-dev isn't updated past 4.4.x headers, there is no guarantee that /usr/include/linux/can/bcm.h contains the proper constant for the userspace API, despite having a supported kernel.
Configuration menu - View commit details
-
Copy full SHA for 56dca1b - Browse repository at this point
Copy the full SHA 56dca1bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0800558 - Browse repository at this point
Copy the full SHA 0800558View commit details -
Configuration menu - View commit details
-
Copy full SHA for f1d212d - Browse repository at this point
Copy the full SHA f1d212dView commit details
Commits on Jul 30, 2019
-
Fix sphinx note directive warning in socket docs
Fix the sphinx warning message that is causing the CI failure: Content block expected for the "note" directive; none found. This is done by increasing the indentation to place the text in a block.
Configuration menu - View commit details
-
Copy full SHA for b28857f - Browse repository at this point
Copy the full SHA b28857fView commit details