-
Notifications
You must be signed in to change notification settings - Fork 380
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
Docs on I2C on the Raspberry Pi are outdated #2716
Comments
[lmbarros] This has attached https://jel.ly.fish/2c01bec6-5d4a-4c5b-9668-9e5fdee085d0 |
@vipulgupta2048 why not link to https://github.com/balena-labs-projects/balena-sense ? It's modern and updated, supports a variety of i2c sensors and is multi-container too |
Sounds good to me! @acostach Let's do that, will you make the PR? |
balena sense would be a better example than the one we currently provide, for sure. FWIW, last Friday I started a little experiment to try these things out myself. For now it is not a good example to share (not documented, and I still have doubts about how it really works), but maybe someday it can become a more focused I2C example. I mean, IMHO, balena sense may be a bit too big as an I2C example. (For example, if you look at the |
@lmbarros your project doesn't look far from being used as a focused example. Looking at balena-sense's docker-compose I believe privileged was used to allow for the sensors to be used with any device-type, regardless of the i2c busses used. Anyway, I opened #2723 to link to it until a more focused example will be available. |
Our docs that explain how to use I2C with the Raspberry Pi family are outdated: they still assume a single container app, while we have been recommending multi-container apps for some time now. The example project we link to is also very old.
(Our docs on multiple containers give some hints on the right way to go, but don't spell out the solution clearly enough either.)
I am not completely sure what a modern I2C example would look like, but here's what I can see for now:
The text was updated successfully, but these errors were encountered: