STRUCT QSEE_REQ_UEFI_SET_VARIABLE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct qsee_req_uefi_set_variable(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual πŸ’– you're literally about to meet struct qsee_req_uefi_set_variable β€” the request struct for the SetVariable command. yes that's its whole vibe. let's get into it ✨


✨ NAME ✨

struct qsee_req_uefi_set_variable β€” literally the Request for the SetVariable command. that's it, that's the name, no cap 🫢


🌸 SYNOPSIS 🌸

struct qsee_req_uefi_set_variable {
    u32 command_id;
    u32 length;
    u32 name_offset;
    u32 name_size;
    u32 guid_offset;
    u32 guid_size;
    u32 attributes;
    u32 data_offset;
    u32 data_size;
 };

look at her. nine u32 fields. main character energy fr fr πŸ‘‘


πŸ¦‹ Members πŸ¦‹

okay so here's the member-by-member breakdown, iykyk:

  • command_id β€” the ID of the command. it must be QSEE_CMD_UEFI_SET_VARIABLE. like, non-negotiable, periodt πŸ’…
  • length β€” length of the request in bytes. and bestie, that includes this struct and any parameters (name, GUID, data) stored after it, plus any padding thereof required for alignment. it's giving "everything counts" 😭
  • name_offset β€” offset from the start of this struct to where the variable name is stored, in bytes. and the name is stored as utf-16 string, so heads up 🌸
  • name_size β€” size of the name parameter in bytes, including null-terminator. don't forget the null-terminator, bestie, it's lowkey important πŸ™ˆ
  • guid_offset β€” offset from the start of this struct to where the GUID parameter is stored, in bytes. yes, more offsets. we love a coordinate system πŸ”₯
  • guid_size β€” size of the GUID parameter in bytes, i.e. sizeof(efi_guid_t). iconic, exact, no guessing ⭐
  • attributes β€” the EFI variable attributes to set for this variable. you're setting the vibes of this variable, literally πŸ’œ
  • data_offset β€” offset from the start of this struct to where the EFI variable data is stored, in bytes. third offset, third slay πŸŽ€
  • data_size β€” size of EFI variable data, in bytes. that's how much actual data you're carrying, ngl πŸ“

🌈 SEE ALSO 🌈

go check these out, they're all part of the friend group:

  • Kernel file ./drivers/firmware/qcom/qcom_qseecom_uefisecapp.c
  • struct qsee_req_uefi_get_variable(9)
  • struct qsee_rsp_uefi_get_variable(9)
  • struct qsee_rsp_uefi_set_variable(9)
  • struct qsee_req_uefi_get_next_variable(9)
  • struct qsee_rsp_uefi_get_next_variable(9)
  • struct qsee_req_uefi_query_variable_info(9)
  • struct qsee_rsp_uefi_query_variable_info(9)

so that's the whole page, bestie β€” every single field, every single byte-count, all present and accounted for πŸ’– this cutie lives in ./drivers/firmware/qcom and the docs are dated October 2026, so mark your calendars πŸ—“οΈβœ¨ k byeee, go read the SEE ALSOs, ily πŸ«ΆπŸ’…

πŸ“¦ where this page comes from