-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update python wrapper to use minimal RF24 constructor #158
Comments
@TMRh20, any plan with this? I guess best would be to check whether RF24 on the system is compiled with BCM support (is that evident from RF24.h?) and depending on that include/exclude BCM-related stuff in the python wrapper? |
Heh, no real plan, just a rough idea. My thoughts initially revolved around removing all the BCM specific stuff from the C++ & python examples, and fixing all the documentation to refer to the standard linux constructor ( like RF24 (22,0) ) while still actually supporting the BCM initialization, just that it would become a mostly undocumented option. This would mainly be to allow some transition time and prevent more confusion around the constructor. Eventually, I think it's probably a good idea to remove the BCM specific stuff altogether, and stick with GPIO + SPI-BUS numbers for Linux devices. |
Python wrapper now exposes BCM specific stuff only if it's in C++ RF24, 95926b2 |
From my point of view it's resolved, closing. |
Reminder to update python wrapper to use minimal RF24 constructor, for use/compatibility with both BCM and SPIDEV usage.
The text was updated successfully, but these errors were encountered: