Skip to content

Conversation

hardbyte
Copy link
Owner

I was going through the examples and found that restarting BCM tasks was broken.

The error is due to a requirement that the transmission task NOT exist in kernel space when sending the restart message. I'm not sure how long it has been broken for.

@hartkopp would you mind checking my logic?

@hardbyte hardbyte mentioned this pull request Nov 17, 2022
hardbyte and others added 2 commits November 18, 2022 14:32
Co-authored-by: zariiii9003 <52598363+zariiii9003@users.noreply.github.com>
@hardbyte hardbyte merged commit 485b1b4 into release-4.1.0 Nov 18, 2022
@hardbyte hardbyte deleted the fix/bcm-socketcan-restartable-tasks branch November 18, 2022 06:28
hardbyte added a commit that referenced this pull request Nov 24, 2022
* Allow restarting of transmission tasks for socketcan * Update can/interfaces/socketcan/socketcan.py Co-authored-by: zariiii9003 <52598363+zariiii9003@users.noreply.github.com>
lumagi added a commit to lumagi/python-can that referenced this pull request Jan 14, 2023
Previously, it was not permitted to restart an already started period send task for SocketCAN. This behavior was changed in PR hardbyte#1440. This commit adjusts the test to reflect this change.
zariiii9003 pushed a commit that referenced this pull request Jan 14, 2023
* Update CI to set up vcan and run SocketCAN tests * Add test to document PyPy raw CAN socket implementation status * Update test for restarting of SocketCAN SendTask Previously, it was not permitted to restart an already started period send task for SocketCAN. This behavior was changed in PR #1440. This commit adjusts the test to reflect this change. * Update PyPy raw CAN socket test failure into warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants