Re: [PATCH 2/2] Support for VIA PadLock crypto engine

[James Morris]

On Wed, 12 May 2004, Michal Ludvig wrote:

> In fact I believe that the hardware-specific drivers (e.g. the S/390 one)
> should be used in the cryptoapi as well and then the kernel should provide
> a single, universal device with read/write/ioctl calls for all of them.
> Not making a separete device for every piece of hardware on the market.
> Am I wrong?

Providing a userspace API is an orthogonal issue, and really needs to be 
designed in conjunction with the async hardware API.

What I am suggesting is that you simply implement something like 
des_z990.c so that C3 users can load crypto alg modules which use their 
hardware.

- James
-- 
James Morris
<jmorris@xxxxxxxxxx>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/