-
Notifications
You must be signed in to change notification settings - Fork 565
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
Modifying to only use one pin for one servo? #6
Comments
Hi, if you use the new userspace servod.c implementation, all you should Richard
|
Hello, Firstly this module is fantastic! I was curious though if you could do the same thing to the kernel driver as well? I was looking at the servoblaster.c code and that it had the following static uint8_t servo2gpio[] = { If I were to comment out all the lines except for pins 4 and 17 would that achieve the same thing? |
@richardghirst Should commenting out still work? I tried that and everything seemed to compile and run fine, but my servo no longer responded to commands. When I first run |
It should still work, but I admit I've not tested that. I'll take a look On Wed, Sep 4, 2013 at 10:36 PM, Jack Minardi notifications@github.comwrote:
|
@richardghirst After restarting my computer and recompiling again it worked for me. Thanks for the awesome software! |
Closing this as you can now specify which pins you want to use for servos via the --p1pins= option to servod. |
What would I need to change in the kernal driver to only have it use one GPIO pin?
The text was updated successfully, but these errors were encountered: