979e93ca24
Just simply provide a device table containing an entry for sun4v cpus, the capability mask checks in the drivers themselves will take care of the rest. This makes the bootup logs on pre-T4 cpus slightly more verbose, with each driver indicating lack of support for the associated opcode(s). But this isn't too much of a real problem. I toyed with the idea of using explicit entries with compatability fields of "SPARC-T4", "SPARC-T5", etc. but all future cpus will have some subset of these opcodes available and this would just be one more pointless thing to do as each new cpu is released with a new string. Signed-off-by: David S. Miller <davem@davemloft.net>
25 lines
923 B
Makefile
25 lines
923 B
Makefile
#
|
|
# Arch-specific CryptoAPI modules.
|
|
#
|
|
|
|
obj-$(CONFIG_CRYPTO_SHA1_SPARC64) += sha1-sparc64.o
|
|
obj-$(CONFIG_CRYPTO_SHA256_SPARC64) += sha256-sparc64.o
|
|
obj-$(CONFIG_CRYPTO_SHA512_SPARC64) += sha512-sparc64.o
|
|
obj-$(CONFIG_CRYPTO_MD5_SPARC64) += md5-sparc64.o
|
|
|
|
obj-$(CONFIG_CRYPTO_AES_SPARC64) += aes-sparc64.o
|
|
obj-$(CONFIG_CRYPTO_DES_SPARC64) += des-sparc64.o
|
|
obj-$(CONFIG_CRYPTO_DES_SPARC64) += camellia-sparc64.o
|
|
|
|
obj-$(CONFIG_CRYPTO_CRC32C_SPARC64) += crc32c-sparc64.o
|
|
|
|
sha1-sparc64-y := sha1_asm.o sha1_glue.o crop_devid.o
|
|
sha256-sparc64-y := sha256_asm.o sha256_glue.o crop_devid.o
|
|
sha512-sparc64-y := sha512_asm.o sha512_glue.o crop_devid.o
|
|
md5-sparc64-y := md5_asm.o md5_glue.o crop_devid.o
|
|
|
|
aes-sparc64-y := aes_asm.o aes_glue.o crop_devid.o
|
|
des-sparc64-y := des_asm.o des_glue.o crop_devid.o
|
|
camellia-sparc64-y := camellia_asm.o camellia_glue.o crop_devid.o
|
|
|
|
crc32c-sparc64-y := crc32c_asm.o crc32c_glue.o crop_devid.o
|