Raspberry Pi example

[jamwaffles]

This should be a good test to exercise the driver. There's still the outstanding question of how we organise examples but having a variety should help people get up and running quickly.

[fmckeogh]

Done :)

Only thrown together very quickly, but does demonstrate some range of the libraries capabilities as well as differences between I2C and SPI interfaces.

Obviously, I'd like to write some kind of guide (pinouts, and detailed code explanation), but was unsure of how you would like this to be integrated into the project.

[jamwaffles]

That's awesome! A section in the readme about Raspi support with a quick getting started guide, small code sample and a link to your examples repo and/or a blog post if you decide to write one would be useful.

What do you think about including the examples in this repo, with a comment stating they might not build out of the box with cargo run --example <name> like the others? It would keep them in the same place at the cost of development ease. How hard would it be to get them working with cargo run --example?

[fmckeogh]

I tried that, and even though I think having different build flags and using cargo build --example pi_graphics_spi --target=armv7-unknown-linux-musleabihf would work, the fact that examples can't have their own dependencies will break everything. Some of the cortex-m crates aren't happy with the Pi target, and one of the Pi dependencies requires std. It's a shame cause it really would be the best option.

What do you think about using a workspace to isolate dependencies? I think just a separate repository might be easiest, but it is an option.

[jamwaffles]

I like the idea of a workspace. It should be possible to test that the RPi examples at least build which is much easier when that code is part of the same project. I'd suggest two sub-folders; ssd1306 and examples-rpi. The Cortex M examples might move into their own workspace later, but that's out of scope for this stuff. Do you have any objections to moving your example code into this repo?

[fmckeogh]

Sounds great!

None at all, I'll have a PR from my fork soon :)

[jamwaffles]

Beaut, thank you!

[chux0519]

@Chocol4te 's example doesn't work now.
I modified it a little bit, and using docker image to cross compile.
here is the working example for now.

[jamwaffles]

Thanks for the fix!

[PatrickLang]

@chux0519 @Chocol4te - are either of you planning to submit this? I did a bit more cleanup https://github.com/PatrickLang/raspi-oled/tree/ctrlc. If you're not planning to open a PR, I'm happy to help. From a legal standpoint it would be best if you could add a license file to your repos so I can do this cleanly as a merge and you'll get credit in the history. Otherwise I can write a sample from scratch and submit it separately.

[chux0519]

@PatrickLang I've added a license to the repo, and for me, feel free to modify that and file a PR

[fmckeogh]

Oops sorry! Which license would be best? The examples I wrote are now 2 years old so do you think its even worth adding mine, especially when https://github.com/chux0519/raspi-oled and https://github.com/PatrickLang/raspi-oled/tree/ctrlc seem a lot more complete?