Subject: Re: Device or pseudo-device for CPU crypto?
To: None <danieldk@pobox.com>
From: Jachym Holecek <freza@dspfpga.com>
List: tech-kern
Date: 01/11/2007 16:39:32
Hello,

# danieldk@pobox.com 2007-01-11:
> I have tried to port OpenBSD support for the VIA Padlock AES logic. It
> seems to be working well now. I am cleaning up the code now and am not
> sure how to represent this. The Padlock is not really a device, since it
> is just an additional CPU instruction.

autoconf(9) is just a tool, you don't need to think too hard about
physical structure of the HW when deciding how you're going to implement
a feature...

(not knowing anything about the Padlock, I can't give more qualified
opinion)

> At any rate, the code requires opencrypto to be initialized (to register
> itself), and rnd.

rnd is initialized before device autoconfiguration, opencrypto is
initialized when the first user calls crypto_get_driverid(). So, no
problem here I think.

	-- Jachym