-
Notifications
You must be signed in to change notification settings - Fork 2.1k
tests: define random default GPIOs to pass Travis builds #2064
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
tests: define random default GPIOs to pass Travis builds #2064
Conversation
|
Hm, I don't really like this. What happens in the case you connect one of these sensors to a board externally? Then you would need to edit the features of that board in order to build... My solution would be to change the default pins to the lowest ones (e.g. GPIO_0, GPIO_1...) and open an issue so that we think about the handling of device drivers in Travis. Sounds feasible? |
2e6b186 to
76326e9
Compare
|
@haukepetersen updated |
tests/driver_l3g4200d/Makefile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about using GPIO_1 here, setting both to the same default port seems awkward, and 2 GPIOs should be fine for almost every board...
|
looks good now, maybe change the one default pint to |
76326e9 to
e7ae2f6
Compare
|
@haukepetersen I did. |
|
ACK when Travis is happy |
|
and Go |
tests: define random default GPIOs to pass Travis builds
These tests fail for boards providing periph_i2c (and periph_gpio) but default pins are not defined correctly.