support for linux version rpi 6.6 #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, thank you for the PR. Somehow I had missed it completely. Since I haven't been coding linux for some time, I'm wondering if this PR should be merged as is or if we should have the old version still available. Could you modify the README.md to document which version of RPi and Linux you tested the changes with. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting from Linux kernel 5.6, the timespec type was replaced by timespec64
replace timespec usage with timespec64 in newer kernel versions to maintain compatibility and avoid potential issues related to the Year 2038 problem.
in newer kernel versions, getnstimeofday() has been deprecated, and it is recommended to use the ktime_get_real_ts64() function instead
method timespec_sub are deprecated in favor of timespec64_sub
ACCESS_ONCE macro has been deprecated in favor of the READ_ONCE and WRITE_ONCE macros
use timespec64_to_ns with the timespec64 structure to avoid issues with the deprecated timespec