GitLab

- Create separate mutex for SPI vs User data handling
Problems:
A: Memory/Data conflicts became apparent after time without thread-safe
queues
B: Without implementing locking at the SPI level, even simple code
examples (rx_transfer.cpp) would hang if a write was done out of sync
with reads

Solutions:
A: Keep initial locking mechanism for users
B: Implement separate automatic mutex and locking mechanism for SPI

#172 #173

per #172 #173

- Add mutex locking to SPI for RPi interrupt usage
- Leave rfInterrupts() rfNoInterrupts() functions for testing purposes

Using interrupts on RPi

Updated bcm library via http://www.airspayce.com/mikem/bcm2835/

http://www.airspayce.com/mikem/bcm2835/bcm2835-1.48.tar.gz

- #include <unistd.h>

- Add current info to news
- Remove old info

Fixed inconsistent documentation, added Tinyx313 pin map

Python3 support added by the fuzzy one.

- For some reason, calling printf before cout results in a hang when
using SPIDEV with RPi
- Add fix for spidev per @mtiutiu #146 & #138

ATtiny2313/4313 support, ATtiny 3 pin mode fix

Update gettingstarted_call_response.cpp

Update gettingstarted.cpp

- Route printf through serial via Serial.printf
- Remove device specific defines & replace with PRIPSTR define for
string ( use of %s vs %S )
- Per @maribeiro #125
- Updated Doxyfile

Add unistd.h for use sleep() in RBpi with kernel 4.1

Required include unistd.h header for use sleep() in RBpi

Signed-off-by: root <mzfuzzy800@gmail.com>

Updated version number

Reduced RAM usage, added a new example, fixed inconsistencies. 

For me it seems there should be no limitation as it should work on any Arduino device + rPi

This is unnecessary and quite a bit outdated file

Rename arch folder for attempted compatibility with Arduino Library
Manager

Update library.properties

Made possible many examples to run in 512 bytes ram chips, fixed few typos, missing F() macro calls and other minor improvements