TEE_DEVICE_ADDRESS_[STRUCT].DATA.BDF(3)

πŸ“¦ version 6.2.6, in arch rolling

πŸ’– NAME πŸ’–

okay bestie, this is the manual page for tee_device_address::[struct].data.bdf. The header calls it tee_device...t].data.bdf(3), and it lives in the Library Functions Manual β€” manual-name vibe folded in right here so we don’t have to copy the header line like a boring person. periodt πŸ’…

πŸ’… SYNOPSIS πŸ’…

here’s the whole map, no cap:

πŸ“¦ Data Structures

  • struct [struct].data.bdf.value β€” that’s the data structure listed. literally it.

πŸŽ€ Public Types

  • enum HECI_HW_TYPE β€” the public type on deck. slay.

🌸 Data Fields

  • struct value β€” a data field, exactly as written.
  • enum hw_type β€” another data field, exactly as written.

πŸ”₯ Detailed Description πŸ”₯

lowkey the whole detailed description is just this:

Definition at line 146 of file metee.h.

🧚 Member Enumeration Documentation 🧚

πŸŒ€ enum

the enum’s full name is a whole keyboard smash, but here it is exactly:

tee_device_address::@135355014054152325330057303335016264100121334037::@254110054145060124165360044220162277306052212243::HECI_HW_TYPE

Specifies HW layout: HECI, FWSTS registers locations β€” that’s the description, periodt. ✨

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for metee from the source code.

not a human author moment β€” just Doxygen doing its automated thing. 🫢


cute sign-off: source/version is metee, page title is tee_device...t].data.bdf(3), and the footer has no date listed, so I’m not inventing one. bye bestie 🫢✨

πŸ“¦ where this page comes from