Tspi_TPM_DirWrite(3)
β¨ Tspi_TPM_DirWrite β¨
okay bestie, welcome to the Tspi_TPM_DirWrite(3) page from the Library Functions Manual, aka the TCG Software Stack Developer's Reference πΈ and yes we are reading a whole manpage together, it's giving study date energy π
π NAME π
Tspi_TPM_DirWrite β write to a Data Integrity Register, no cap π
π¦ SYNOPSIS π¦
#include <tss/platform.h>
#include <tss/tcpa_defines.h>
#include <tss/tcpa_typedef.h>
#include <tss/tcpa_struct.h>
#include <tss/tss_typedef.h>
#include <tss/tss_structs.h>
#include <tss/tspi.h>
TSS_RESULT Tspi_TPM_DirWrite(TSS_HTPM hTPM, UINT32 ulDirIndex,
UINT32 ulDirDataLength, BYTE* rgbDirData);
like, look at those includes, so many headers, she's thorough π
π DESCRIPTION π
Tspi_TPM_DirWrite writes a data integrity register, periodt. βοΈ
Bestie, the vibe check here is: you gotta already know which DIR index you're writing to and what data you're putting in there before you even call this command. It does not hold your hand, it does not guess, it just writes. So come prepared π
π§ PARAMETERS π§
hTPM
The hTPM parameter is used to specify the handle of the TPM object. literally the "which TPM are we talking to" of it all π
ulDirIndex
The ulDirIndex parameter is the index of the DIR to write. π― Wanna know how many DIR registers your TPM even supports? Use Tspi_TPM_GetCapability(3) β she'll tell you, iykyk.
ulDirDataLength
The ulDirDataLength parameter is the length in bytes of the rgbDirData parameter. yes bestie, it's the length of the data, we love a matching pair π«
rgbDirData
The rgbDirData parameter is a pointer to memory containing the data to be written to the DIR. just a lil pointer, pointing at your precious bytes π«Ά
π₯ RETURN CODES π₯
Tspi_TPM_DirWrite returns TSS_SUCCESS on success π otherwise one of the following values is returned:
TSS_E_INVALID_HANDLEβhTPMis not a valid handle. like, who is she?? not a real handle πTSS_E_INTERNAL_ERRORβ An internal SW error has been detected. something went wrong in the software guts, not your fault (probably) πTSS_E_BAD_PARAMETERβ One or more parameters is bad. bestie check ur args π
π CONFORMING TO π
Tspi_TPM_DirWrite conforms to the Trusted Computing Group Software Specification version 1.1 Golden β she follows the rules, she's certified, she's iconic.
πΈ SEE ALSO πΈ
go read those too, we love a cross-reference moment π
okay that's the whole page, bestie!! this one came from TSS 1.1, dated 2004-05-25, and it lives in the Library Functions Manual π thanks for reading with me, mwah, slay, bye πβ¨
π¦ where this page comes from
- debian bookworm: libtspi-dev 0.3.15-0.3 Β· BSD-3-Clause
- debian trixie: libtspi-dev 0.3.15-0.4 Β· BSD-3-Clause
- epel 10: trousers-devel 0.3.15-11.el10_0 Β· BSD
- epel 9: trousers-devel 0.3.15-5.el9 Β· BSD
- fedora 43: trousers-devel 0.3.15-15.fc43 Β· LicenseRef-Callaway-BSD
- fedora 43: trousers-devel 0.3.15-15.fc43 Β· LicenseRef-Callaway-BSD
- fedora 43: trousers-devel 0.3.15-16.fc43 Β· LicenseRef-Callaway-BSD
- fedora 43: trousers-devel 0.3.15-16.fc43 Β· LicenseRef-Callaway-BSD
- fedora 44: trousers-devel 0.3.15-17.fc44 Β· LicenseRef-Callaway-BSD
- fedora 44: trousers-devel 0.3.15-17.fc44 Β· LicenseRef-Callaway-BSD
- nixos 26.05: trousers 0.3.15
- nixpkgs unstable: netbsd-source 11.0
- nixpkgs unstable: trousers 0.3.15
- opensuse-leap 16.0: trousers-devel 0.3.15-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: trousers-devel 0.3.15-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: trousers-devel 0.3.15-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: trousers-devel 0.3.15-160000.2.2 Β· BSD-3-Clause
- ubuntu jammy: libtspi-dev 0.3.15-0.2 Β· BSD-3-Clause
- ubuntu noble: libtspi-dev 0.3.15-0.3build2 Β· BSD-3-Clause
- ubuntu questing: libtspi-dev 0.3.15-0.4
- ubuntu resolute: libtspi-dev 0.3.15-1 Β· BSD-3-Clause
- ubuntu stonking: libtspi-dev 0.3.15-1ubuntu2 Β· BSD-3-Clause
- Copyright (C) 2004 International Business Machines Corporation
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms