Ludwig Knüpfer

> see also -> #4758 The relevant part seems to be @haukepetersen writing there is a need for thread-safety of these APIs. I could not see any objections to this...

Sure, we can split the realtime side-effects documentation to a separate issue. Maybe it's more purposeful to provide some tool for the task of identifying the possible side-effects anyways.

@kaspar030 did create an issue already: https://github.com/RIOT-OS/RIOT/issues/4872

Works for me.

Learn some Linux and fix the permissions ;-) With permissions set up correctly, sudo is not required: ``` pi@pi:~/MFRC522-python $ ls -l /dev/spidev0.* crw-rw---- 1 root spi 153, 0 Dec...

Compare https://github.com/mxgxw/MFRC522-python/issues/36

I'm using this now and I'm happy with it: https://github.com/ondryaso/pi-rc522

Nevermind - a useful successor exists: https://github.com/ondryaso/pi-rc522

Compare https://github.com/mxgxw/MFRC522-python/issues/36

Here is an ugly hack that adds interrupt driven support for waiting for a card detect event. ```diff diff --git a/MFRC522.py b/MFRC522.py index 6f157c2..735f036 100644 --- a/MFRC522.py +++ b/MFRC522.py @@...