haxan:
Is there anyway i can know if the h/w is being touched in those libraries?
If the module includes an AVR specific header file then it is probably touching hardware directly.
Things like
#include <wdt.h>
#include <pgmspace.h>
#include <eeprom.h>
#include <util/delay.h>
#include <util/atmoic.h>
#include <avr/{anything}.h>
are sure signs that there is likely to be AVR proprietary code involved.
The only reason there wouldn't be is if the header was included by accident and not used.
Then there are some other things like the AVR proprietary PROGMEM stuff:
PROGMEM, prog_char, progmem etc... to look for.
You can also look for AVR registers being used. Things like:
PORTA, PORTB, ..., PORTG, etc
Timer registers:
TIMSK2, TOIE2, TCCR2A, TCCR2B, ASSR, TIMSK2, OCIE2A, etc...
Anything that uses interrupts or timers will definitely have issues.
The reason being that the Arduino environment does not provide
APIs for interrupts or timers so anything that needs this has to step
outside Arduino and talk to the h/w directly.
If you are using Paul's Teensy 3 boards instead of DUE, there are some compatibility
macros/templates/classes that provide some additional level of AVR compatibility
that the Arduino DUE support provided by team Arduino does not provide.