On 11 April 2015 at 10:48, Arnd Bergmann a...@arndb.de wrote:
On Saturday 11 April 2015 09:35:15 Ard Biesheuvel wrote:
On 10 April 2015 at 22:23, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
On 10 apr. 2015, at 22:08, Arnd Bergmann a...@arndb.de wrote:
On Friday 10 April 2015 16:29:08
On Saturday 11 April 2015 12:27:18 Ard Biesheuvel wrote:
Ah i see it now. The new Sha256 module as well as the Sha512 i am proposing
here both use a single .o containing the !neon and neon implementations, and
only expose the latter if KERNEL_MODE_NEON. This way, we can use the exact
same
On Saturday 11 April 2015 12:35:19 Ard Biesheuvel wrote:
Yes, that should work. Could we also move the CE objs to ce-obj-$() and put
ifneq ($(ce-obj-y)$(ce-obj-m),)
if as check
obj-y += $(ce-obj-y)
obj-m += $(ce-obj-m)
else
$(warning ...)
endif
endif
around it so you only get the
Am Samstag, 11. April 2015, 09:07:35 schrieb sri sowj:
Hi sri,
Hi Stephen,
Thanks a million for the information provided. I really appreciate
your time and efforts.
In CTR mode counter size is not fixed , it varies based on
requirements like for rfc 3686 its size is 4 bytes, for other
On 10 April 2015 at 21:57, Arnd Bergmann a...@arndb.de wrote:
Old versions of binutils (before 2.23) do not yet understand the
crypto-neon-fp-armv8 fpu instructions, and an attempt to build these
files results in a build failure:
arch/arm/crypto/aes-ce-core.S:133: Error: selected processor
On Saturday 11 April 2015 09:35:15 Ard Biesheuvel wrote:
On 10 April 2015 at 22:23, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
On 10 apr. 2015, at 22:08, Arnd Bergmann a...@arndb.de wrote:
On Friday 10 April 2015 16:29:08 Ard Biesheuvel wrote:
+#if __ARM_MAX_ARCH__=7
+.arch
On Saturday 11 April 2015 09:41:08 Ard Biesheuvel wrote:
Could you perhaps put the rules that build these modules inside a
ifneq ($(armv8-ce-flags),-DARMV8_CE_DISABLED)
...
endif
How about something like this:
ifeq ($(call as-option,-Wa$(comma)-mfpu=crypto-neon-fp-armv8),)
$(warning
On 10 April 2015 at 22:23, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
On 10 apr. 2015, at 22:08, Arnd Bergmann a...@arndb.de wrote:
On Friday 10 April 2015 16:29:08 Ard Biesheuvel wrote:
+#if __ARM_MAX_ARCH__=7
+.arch armv7-a
+.fpu neon
+
This will cause a build failure on an
From: Arnd Bergmann a...@arndb.de
How about something like this:
A warning will be emitted by make when descending into the arch/arm/crypto
directory, but only if any ARMv8 Crypto modules were in fact selected.
/home/ard/linux-2.6/arch/arm/crypto/Makefile:22: These ARMv8 Crypto Extensions
sri sowj srisowj4li...@gmail.com wrote:
I have seen multiple open source drivers for AES(CTR) mode for
different Crypto Hardware Engines, I was not really sure on
countersize,nonce etc.
Please can any one provide some info on the following
Not what you asked for, but in case it is useful
On 11 apr. 2015, at 10:48, Arnd Bergmann a...@arndb.de wrote:
On Saturday 11 April 2015 09:35:15 Ard Biesheuvel wrote:
On 10 April 2015 at 22:23, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
On 10 apr. 2015, at 22:08, Arnd Bergmann a...@arndb.de wrote:
On Friday 10 April 2015
On 11 apr. 2015, at 10:55, Arnd Bergmann a...@arndb.de wrote:
On Saturday 11 April 2015 09:41:08 Ard Biesheuvel wrote:
Could you perhaps put the rules that build these modules inside a
ifneq ($(armv8-ce-flags),-DARMV8_CE_DISABLED)
...
endif
How about something like this:
ifeq
DO YOU NEED LOAN?
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
13 matches
Mail list logo
