Wyllys Ingersoll wrote:
Darren J Moffat wrote:
a crypto framework plugin in the kernel *is* a driver. Is the
intention to just initially provide access to the TPM via the crypto
framework ? or are there other APIs that these TPM drivers will be
providing to something other than the crypto framework ?
From what I understand, he has built a device driver for the
chip and now he wants to add a module that sits above the driver
to bind it to the crypto framework. It sounds like 2 different
modules, but I haven't seen the code or anything yet.. All the more
reason to get them on opensolaris...
So lets start with this in the crypto project so we can get this info.
Here is what I want - I want them to be able to manage their own area -
posting files, documents, and have their own mailing list for TPM related
discussions. Can this be done under the existing crypto project or not?
Do we really need yet another mail list initially ? Could we start using
the crypto-discuss list and if it gets too much then create an
additional TPM one ? This is what we are doing for bluetooth stack for
example.
For the code they would get their own source repositories that they
would be able to push/pull code from - that may or may not be clones of
the ON gate. This is what we are doing for the VIA drivers.
For content on the web page I'd be happy to give them access and
subpages of crypto project to host info on the TPM drivers.
I'm not opposed to, in fact I think we would very much need, a separate
project once we start doing stuff with TCG other than using them just
through the crypto framework. It seems at the moment though that this
is just making the TPM usable to the crypto framework, right ? if thats
the case the crypto project is in my opinion the best place.
--
Darren J Moffat
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
