OSCAR wrote: ... > How can I use the SPI directly for SPARC T2 Hardware crypto module?
This is neither supported nor documented. > I don't want to be scheduling or load balancing by KCF. I recommend that you use the *_prov variant of the KCF API, if you want the above (i.e. always use the T2 hardware provider) - crypto_get_provider(...), and crypto_encrypt_prov(...) etc. These routines are akin to calling the SPI directly. -Krishna