forked from adafruit/adafruit-beaglebone-io-python
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make friends between 3.8 and 4.1+ kernels
- Loading branch information
plawler
committed
Apr 29, 2016
1 parent
d9ad2b3
commit d16654d
Showing
3 changed files
with
67 additions
and
10 deletions.
There are no files selected for viewing
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
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
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
d16654d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Any plans to do a PR on this work into Adafruit's original repo? If so, I'll back out my PR that fix this in a slightly different way (w/o the macros, so my fix addresses this during runtime). I like your fix better though.
d16654d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
I'm currently in two minds about whether to do a PR into Adafruit. Reading around their forums, it'd seem they've got someone to work on this themselves, so I don't particularly want to step on their toes. I did draw attention to this change to someone on their forums who seems BBB knowledgable and figured I'd give them a few weeks to check it out and see what they think before deciding what to do next.
One thing's recently come to mind is that the kernel version check is very lazy and could probably be tightened, I wouldn't be keen on doing a PR without fixing that a little first.
Also, looking over the code again, it'd seem I got an edit wrong from my test environment (which isn't connected to the Internet thus I did a bit of a manual hack change... I'll def have to check out the common.h change as that really doesn't look right)
d16654d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cleaned up the diff some more and submitted a PR. Thanks for poking me about this, Simplicity. It would've sat in the bottom drawer if it had not been for you π