Read Status Byte when communicating on SPI about cc1101 HOT 3 CLOSED

Is the status byte really appropriate to give access to or should its meaning be conveyed via api behavior instead? Would be great if you could provide some psuedo code examples.

from cc1101.

1. There will be indirect access to the "status byte", given in a semantical way (not raw byte)
2. If the user wishes, he can access the last Chip Status Byte after performing an SPI transaction (calling any functional lib's API)
3. Reading the "status byte" in the "lowlevel" doesn't add much overhead, since the SPI already transferred us the status byte from CC1101
4. As a device driver, (this repo) shall implement (ideally) all of the device's capabilities - "status byte" is one of them
5. I will provide the implementation with upcoming PR

from cc1101.

resolved via #41

from cc1101.