-
Notifications
You must be signed in to change notification settings - Fork 72
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
Using wiringPi instead bcm2835 #10
base: master
Are you sure you want to change the base?
Conversation
Makes node-dht-sensor compatible with banana pi.
This is very good! I was thinking of using wiringPi for sometime now. |
Yes I have a Banana Pi and it works like a charm. |
Yeah, you're right! It was the pin numbering that is different. |
What about my fix? |
Why are you using wiringPi, instead of BCM2835 directly? |
Because i have an banana pi ;)
|
Ok, I understand. You have a fair point and your implementation is good. The problem is that wiringPi not only adds another dependency to the project but also breaks compatibility with existing GPIO numbering convention. Therefore, this change would affect many applications already deployed out there and I really want to avoid this problem. Because the bananaPi also uses the BCM2835 chip it should be possible to access the GPIO in a similar way without requiring wiringPi but so far I did not find any references to this approach. Perhaps a closer look into wiringPi may reveal how to implement this. |
Thanks for the changes Xento, based on them I can now run my script without sudo. |
Makes node-dht-sensor compatible with banana pi.