> I have tried to port OpenBSD support for the VIA Padlock AES logic.
> [...]  I am [...] not sure how to represent this.  The Padlock is not
> really a device, since it is just an additional CPU instruction.  I
> would call it a pseudo-device, though I haven't seen (m)any
> hardware-bound pseudodevices.

I'd probably make it a device, attaching at mainbus if you don't have
anywhere else to put it - while it sounds as though it really ought to
attach "at cpu", I don't know how easy that would be to arrange.

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

> Any ideas?

So, defer some of its initialization until the first attempt to use it?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B