11 Dec, 2006
1 commit
-
This driver seems to be for a PCI device.
drivers/crypto/geode-aes.c:384: warning: implicit declaration of function 'pci_release_regions'
drivers/crypto/geode-aes.c:397: warning: implicit declaration of function 'pci_request_regions'Signed-off-by: Randy Dunlap
Acked-by: Jordan Crouse
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
07 Dec, 2006
2 commits
-
On Tue, Nov 14, 2006 at 01:41:25AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.19-rc5-mm2:
>...
> git-cryptodev.patch
>...
> git trees
>...This patch makes the needlessly global geode_aes_crypt() static.
Signed-off-by: Adrian Bunk
Signed-off-by: Herbert Xu -
Add a driver to support the AES hardware on the Geode LX processor.
Signed-off-by: Jordan Crouse
Signed-off-by: Herbert Xu
21 Sep, 2006
13 commits
-
This patch converts padlock-sha to use crypto_hash for its fallback.
It also changes the fallback selection to use selection by type instead
of name. This is done through the new CRYPTO_ALG_NEED_FALLBACK bit,
which is set if and only if an algorithm needs a fallback of the same
type.Signed-off-by: Herbert Xu
-
This patch converts all users to use the new crypto_comp type and the
crypto_has_* functions.Signed-off-by: Herbert Xu
-
This patch removes obsolete block operations of the simple cipher type
from drivers. These were preserved so that existing users can make a
smooth transition. Now that the transition is complete, they are no
longer needed.Signed-off-by: Herbert Xu
-
This patch adds block cipher algorithms for cbc(aes) and ecb(aes) for
the PadLock device. Once all users to the old cipher type have been
converted the old cbc/ecb PadLock operations will be removed.Signed-off-by: Herbert Xu
-
Now that the tfm is passed directly to setkey instead of the ctx, we no
longer need to pass the &tfm->crt_flags pointer.This patch also gets rid of a few unnecessary checks on the key length
for ciphers as the cipher layer guarantees that the key length is within
the bounds specified by the algorithm.Rather than testing dia_setkey every time, this patch does it only once
during crypto_alloc_tfm. The redundant check from crypto_digest_setkey
is also removed.Signed-off-by: Herbert Xu
-
TFMs are local variables. No need to declare them
static. After all one is enough.Signed-off-by: Michal Ludvig
Signed-off-by: Herbert Xu -
Compile a helper module padlock.ko that will try
to autoload all configured padlock algorithms.This also provides backward compatibility with
the ancient times before padlock.ko was renamed
to padlock-aes.koSigned-off-by: Michal Ludvig
Signed-off-by: Herbert Xu -
This patch makes two needlessly global functions static.
Signed-off-by: Adrian Bunk
Signed-off-by: Herbert Xu -
Support for SHA1 / SHA256 algorithms in VIA C7 processors.
Signed-off-by: Michal Ludvig
Signed-off-by: Herbert Xu -
PADLOCK_CRA_PRIORITY is shared between padlock-aes and padlock-sha
so it should be in the header.On the other hand "struct cword" is only used in padlock-aes.c
so it's unnecessary to have it in padlock.hSigned-off-by: Michal Ludvig
Signed-off-by: Herbert Xu -
Whenever we rename modules we should add an alias to ensure that existing
users can still locate the new module.This patch also gets rid of the now unused module function prototypes from
padlock.h.Signed-off-by: Herbert Xu
-
Merge padlock-generic.c into padlock-aes.c and compile
AES as a standalone module. We won't make a monolithic
padlock.ko with all supported algorithms, instead we'll
compile each driver into its own module.Signed-off-by: Michal Ludvig
Signed-off-by: Herbert Xu -
The crypto API is made up of the part facing users such as IPsec and the
low-level part which is used by cryptographic entities such as algorithms.
This patch splits out the latter so that the two APIs are more clearly
delineated. As a bonus the low-level API can now be modularised if all
algorithms are built as modules.Signed-off-by: Herbert Xu
15 Jul, 2006
1 commit
-
Herbert's patch 82062c72cd643c99a9e1c231270acbab986fd23f
in cryptodev-2.6 tree breaks alignment rules for PadLock
xcrypt instruction leading to General protection Oopses.This patch fixes the problem.
Signed-off-by: Michal Ludvig
Signed-off-by: Herbert Xu
26 Jun, 2006
2 commits
-
i386 assembly has more compact instructions for accessing 7-bit offsets.
So by moving the large members to the end of the structure we can save
quite a bit of code size. This patch shaves about 10% or 300 bytes off
the padlock-aes file.Signed-off-by: Herbert Xu
-
Up until now algorithms have been happy to get a context pointer since
they know everything that's in the tfm already (e.g., alignment, block
size).However, once we have parameterised algorithms, such information will
be specific to each tfm. So the algorithm API needs to be changed to
pass the tfm structure instead of the context pointer.This patch is basically a text substitution. The only tricky bit is
the assembly routines that need to get the context pointer offset
through asm-offsets.h.Signed-off-by: Herbert Xu
21 Mar, 2006
1 commit
-
Since tfm contexts can contain arbitrary types we should provide at least
natural alignment (__attribute__ ((__aligned__))) for them. In particular,
this is needed on the Xscale which is a 32-bit architecture with a u64 type
that requires 64-bit alignment. This problem was reported by Ronen Shitrit.The crypto_tfm structure's size was 44 bytes on 32-bit architectures and
80 bytes on 64-bit architectures. So adding this requirement only means
that we have to add an extra 4 bytes on 32-bit architectures.On i386 the natural alignment is 16 bytes which also benefits the VIA
Padlock as it no longer has to manually align its context structure to
128 bits.Signed-off-by: Herbert Xu
22 Feb, 2006
1 commit
-
A typo crept into the le32_to_cpu patch which broke 256-bit keys
in the padlock driver. The following patch based on observations
by Michael Heyse fixes the problem.Signed-off-by: Herbert Xu
Signed-off-by: Linus Torvalds
10 Jan, 2006
3 commits
-
As the Crypto API now allows multiple implementations to be registered
for the same algorithm, we no longer have to play tricks with Kconfig
to select the right AES implementation.This patch sets the driver name and priority for all the AES
implementations and removes the Kconfig conditions on the C implementation
for AES.Signed-off-by: Herbert Xu
-
A lot of crypto code needs to read/write a 32-bit/64-bit words in a
specific gender. Many of them open code them by reading/writing one
byte at a time. This patch converts all the applicable usages over
to use the standard byte order macros.This is based on a previous patch by Denis Vlasenko.
Signed-off-by: Herbert Xu
-
Change the bit-field in struct cword to unsigned to shut sparse up.
Signed-off-by: Herbert Xu
31 Oct, 2005
1 commit
-
Add CONFIG_X86_32 for i386. This allows selecting options that only apply
to 32-bit systems.(X86 && !X86_64) becomes X86_32
(X86 || X86_64) becomes X86Signed-off-by: Brian Gerst
Cc: Sam Ravnborg
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
07 Jul, 2005
4 commits
-
When the Padlock does CBC encryption, the memory pointed to by EAX is
not updated at all. Instead, it updates the value of EAX by pointing
it to the last block in the output. Therefore to maintain the correct
semantics we need to copy the IV.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller -
This patch ensures that cit_iv is aligned according to cra_alignmask
by allocating it as part of the tfm structure. As a side effect the
crypto layer will also guarantee that the tfm ctx area has enough space
to be aligned by cra_alignmask. This allows us to remove the extra
space reservation from the Padlock driver.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller -
By operating on multiple blocks at once, we expect to extract more
performance out of the VIA Padlock.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller -
Most of the work done aes_padlock can be done in aes_set_key. This
means that we only have to do it once when the key changes rather
than every time we perform an encryption or decryption.This patch also sets cra_alignmask to let the upper layer ensure
that the buffers fed to us are aligned correctly.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
