On Mon, Oct 08, 2007 at 05:49:39PM +0200, Sebastian Siewior wrote:
>
> After thinking I realized that he does not need to provide an alias
> because his driver should be auto loaded due to the PCI-IDs right?
Good point.
> But while you mention it: Should the alias cbc(aes), etc. also be
> provid
* Herbert Xu | 2007-10-08 11:15:10 [+0800]:
>On Sat, Oct 06, 2007 at 11:58:57PM +0200, Sebastian Siewior wrote:
>> * Evgeniy Polyakov | 2007-10-02 19:00:13 [+0400]:
>>
>> >+MODULE_LICENSE("GPL");
>> >+MODULE_AUTHOR("Evgeniy Polyakov <[EMAIL PROTECTED]>");
>> >+MODULE_DESCRIPTION("Driver for HIFN
There are currently several SHA implementations that all define their own
initialization vectors and size values. Since this values are idential
move them to a header file under include/crypto.
The Patch should apply to cryptodev-2.6.
Signed-off-by: Jan Glauber <[EMAIL PROTECTED]>
---
arch/s390/
* Herbert Xu | 2007-10-08 11:20:17 [+0800]:
>On Sun, Oct 07, 2007 at 11:42:27PM +0200, Sebastian Siewior wrote:
>>
>> I tried to deadlock and I did not succeed, maybe I did something wrong.
>>
>> # fgrep sha modules.alias
>> alias sha256 padlock_sha
>> alias sha1 padlock_sha
>> alias sha384 sha
* Jan Glauber | 2007-10-08 13:25:23 [+0200]:
>Hi Sebastian,
Hi Jan, good to see you back :)
>what about SHA-512? Should that not also be renamed to sha512_generic.c ?
We could do it, but I haven't seen a HW implementation yet. If your new
CPU has an opcode for this, we could rename it than :)
>
Hi Sebastian,
what about SHA-512? Should that not also be renamed to sha512_generic.c ?
--Jan
On Thu, 2007-10-04 at 09:37 +0200, Sebastian Siewior wrote:
> Loading the crypto algorithm by the alias instead of by module directly
> has the advantage that all possible implementations of this algori
