The Octeon Crypto functions are available in the kernel, under the Cryptographic API section, but I believe it wouldn't apply to the Octeon+/OcteonII, only the OcteonIII CN7xxx and higher. The entire Octeon target is locked to the Octeon+ (Octeon 1.5) via -march in the target defines.
We've had discussions and issues regarding the increasing spread of the Octeon targets across the various revisions. Octeon+ is inhibiting the OcteonIII targets, but in order to maintain compatibility with the ERlite, it has to be this way.. There aren't enough OcteonIII targets to justify a new target in terms of build resources.
