Skip to content
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

Ported to work with WiringPi #1

Merged
merged 1 commit into from
May 9, 2014
Merged

Ported to work with WiringPi #1

merged 1 commit into from
May 9, 2014

Conversation

jfktrey
Copy link

@jfktrey jfktrey commented May 9, 2014

The plain GPIO version of librf24-rpi was modified to work with the WiringPi library instead of the (custom?) compatibility layer. Very useful for individuals like me who wish to use both librf24-rpi and WiringPi, but previously couldn't due to incompatibilities. WiringPi was (pretty much) a drop-in replacement for the functions used in the GPIO version.

The plain GPIO version of librf24-rpi was modified to work with the
WiringPi library instead of the compatibility layer.
stanleyseow added a commit that referenced this pull request May 9, 2014
Ported to work with WiringPi
@stanleyseow stanleyseow merged commit 5c01b46 into stanleyseow:master May 9, 2014
@gnulnulf
Copy link
Collaborator

gnulnulf commented May 9, 2014

Maybe it's a good idea to obsolete the old library..Probably no one uses it anymore.

@stanleyseow
Copy link
Owner

How do I obsolete the old library ??

Or how do I update them to the latest commits..

Stanley

On Fri, May 9, 2014 at 9:02 PM, Arco van Geest notifications@github.comwrote:

Maybe it's a good idea to obsolete the old library..Probably no one uses
it anymore.


Reply to this email directly or view it on GitHubhttps://github.com//pull/1#issuecomment-42663082
.

Stanley Seow

http://about.me/stanleyseow/bio

@hallard
Copy link
Collaborator

hallard commented Jun 11, 2014

Hi Guys,
I'm the author of the librf24-bcm which is obviously the librf24 version for NRF24 of Stanley rebranded to use low level I/O control with BCM chipset of the PI.
I totally agree, having too much libraries may confuse users and define just one will help them.
By the way on my library I've added a features to be able a custom GPIO to act as chip select pin for SPI and also a function to detect PI version (V1 or V2)
I found that when tried to use CE1 (2nd spi bus) the PI continued to drive with CE0 which mainly removed me the ability to use 2 SPI devices (one on CE0 and the other on CE1). So in my library I was driving CE1 manually (but may be now, kernel is updated and works fine)
So if you want to integrate these 2 features in jfktrey library I can stop using mine and use the new one. No problem, just let me know.
Charles

stanleyseow pushed a commit that referenced this pull request Aug 3, 2014
Merge improved write_payload() and read_payload()  - looks good and passes my testing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants