Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
wrote on 09/20/2016 06:04:23 AM:

=
> 
> On Mon, Sep 19, 2016 at 10:50:15AM -0400, Stefan Berger wrote=
:
> >    > You also fail to explain how this should w=
ork
with ACPI even though
> >    > we know that there doe=
s not exist any kind
for event log through ACPI
> >    > with TPM 2.0 hard=
ware. I.e. just by reading
the commits I canobviously
> >    > see that you are =
doing major untested code
path changes.
> > 
> >    That's true there the=
re's not spec for a BIOS at
the moment and I would
> >    expect that TCG will likel=
y not write one. Likely
all vendors have moved
> >    on to (U)EFI. We realized =
this also while implementing
TPM 2 support for
> >    SeaBIOS and I ended up reusing =
the ACPI TCPA table
but adopted the EFI
> >    specified log format with tha=
t special first entry.
Can we 
> accomodate that
> >    ?
> 
>=
; Does that match to "SHA1 Event Log Entry Format" defined
in [1]? In
> addition "Crypto Agile Log Entry Format" must =
be supported.
SeaBIOS supports the SH=
A1 Event Log Entry Format [5.1
in that spec]. It uses it for TPM 1.2.
https://code.coreboot.org/p/seabios/source/tree/mas=
ter/src/std/tcg.h#L521
In case of=
 TPM 2 it will write the first log entry
in the format of the Event Log Header [5.3].
All =
subsequent entries in the log will be written
in Crypto Agile Log Entry Format [5.2].
Again: 
https://co=
de.coreboot.org/p/seabios/source/tree/master/src/std/tcg.h#L521
UEFI may write into some special buffer that=
 the OS
can get to via an API call. In case of SeaBIOS this buffer is just in the
TCPA ACPI table, as in TPM 1.2.

&=
gt; 
> Philip: what was the UEFI handover procedure that was discusse=
d in
> TPM BoF at LSS 2016?
> 
> >      =
; Stefan
> 
> [1] 
http://www.trust=
edcomputinggroup.org/wp-content/uploads/EFI-

> Protocol-Specification-rev13-160330final.pdf
> 
>=
 /Jarkko
> 