Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ClockVapor/rpi_gpio issues and pull requests
#28 - Wrong ELF class on RPZ2
Issue -
State: open - Opened by daBee almost 3 years ago
- 2 comments
#27 - not running on a RPi
Issue -
State: open - Opened by daBee almost 3 years ago
- 2 comments
#26 - Use externs in common.h
Pull Request -
State: open - Opened by synthead about 3 years ago
#25 - Cannot open shared object
Issue -
State: open - Opened by MarioRuiz almost 4 years ago
- 9 comments
#24 - rpi_gpio.so compiled as 32-bit on 64-bit system
Issue -
State: open - Opened by vanne over 4 years ago
- 3 comments
#23 - Can't require gem on RPi 3B+
Issue -
State: closed - Opened by egor-khanko over 4 years ago
- 1 comment
#22 - Can't Require Gem on RPi 4
Issue -
State: open - Opened by aaronmiler over 4 years ago
- 9 comments
#21 - is this only for raspberry pi?
Issue -
State: closed - Opened by polarspetroll over 4 years ago
- 1 comment
#20 - Update to raspberry-gpio-python version 0.7.
Pull Request -
State: open - Opened by francois2metz over 4 years ago
- 6 comments
#19 - Doesn't work properly with more than 2 LEDs
Issue -
State: open - Opened by Souravgoswami over 5 years ago
- 4 comments
#18 - Allows setup and high/low to accept an array of pin numbers
Pull Request -
State: closed - Opened by codenamev almost 6 years ago
- 2 comments
#17 - Allows setup and high/low to accept multiple pins
Pull Request -
State: closed - Opened by codenamev over 6 years ago
- 3 comments
#16 - event_detected() function
Issue -
State: open - Opened by luisjoseve over 7 years ago
- 1 comment
#15 - Keep up!
Issue -
State: open - Opened by dzmitrys-dev over 7 years ago
#14 - How to read the status of an output pin
Issue -
State: closed - Opened by shaliko almost 8 years ago
- 2 comments
#13 - Emulation of GPIO
Issue -
State: open - Opened by mikebaldry about 8 years ago
- 1 comment
#12 - Toggle method
Issue -
State: open - Opened by kochka about 8 years ago
#11 - Change RuntimeError to warning when the gem fails to detect RPi hardware
Pull Request -
State: closed - Opened by brundage about 8 years ago
- 1 comment
#10 - Fix missing variable declarations.
Pull Request -
State: closed - Opened by nsatragno over 8 years ago
- 1 comment
#9 - Re-request pull "add :initialize argument to :output mode"
Pull Request -
State: closed - Opened by iohzrd over 8 years ago
#8 - Revert "add :initialize argument to :output mode"
Pull Request -
State: closed - Opened by ClockVapor over 8 years ago
#7 - wrong commit author
Issue -
State: closed - Opened by iohzrd over 8 years ago
- 4 comments
#6 - add :initialize argument to :output mode
Pull Request -
State: closed - Opened by iohzrd over 8 years ago
#5 - Channels switch on(low) when setting to output.
Issue -
State: closed - Opened by iohzrd over 8 years ago
- 4 comments
Labels: task
#4 - Implement event-driven input
Issue -
State: closed - Opened by ClockVapor over 8 years ago
- 18 comments
Labels: task
#3 - Update to RPi.GPIO 0.6.2
Issue -
State: closed - Opened by ClockVapor almost 9 years ago
Labels: enhancement
#2 - Trying to run this gem within Docker, however it returns the error 'RuntimeError: this gem can only be run on a Raspberry Pi'
Issue -
State: closed - Opened by jrobertson over 9 years ago
- 3 comments
#1 - for now no compatibility for bcm2709 on the raspberry pi2 ?
Issue -
State: closed - Opened by hugoerg56 over 9 years ago
- 1 comment