STRUCT QSEE_RSP_UEFI_GET_NEXT_VARIABLE(9)

💖 struct qsee_rsp_uefi_get_next_variable(9) — Kernel API Manual 💖

Okay bestie, welcome to the Kernel API Manual entry for this struct. We're gonna get into the layout, the offsets, and all the little byte details. No cap, it's giving response-struct energy. ✨

🌸 NAME 🌸

struct qsee_rsp_uefi_get_next_variable — the response for the GetNextVariableName command. That's the whole vibe. 💅

✨ SYNOPSIS ✨

The shape of it is literally:

struct qsee_rsp_uefi_get_next_variable {
    u32 command_id;
    u32 length;
    u32 status;
    u32 guid_offset;
    u32 guid_size;
    u32 name_offset;
    u32 name_size;
 };

🎀 Members 🎀

• command_id — the ID of the command. It should be QSEE_CMD_UEFI_GET_NEXT_VARIABLE. iykyk 💫
• length — the length of the response, in bytes. It includes this struct and any parameters (name, GUID) stored after it, plus any padding thereof for alignment. She counts the padding too, bestie — thorough queen. 👑
• status — the status of this command. Simple as that. Vibe check in u32 form. ✅
• guid_offset — offset from the start of this struct to where the GUID parameter is stored, in bytes. Follow the bytes, follow the bytes. 🦋
• guid_size — size of the GUID parameter in bytes, i.e. sizeof(efi_guid_t). Iconic little sizeof moment. 🎀
• name_offset — offset from the start of this struct to where the variable name is stored (as utf-16 string), in bytes. Name hunt activated. 🔍
• name_size — size of the name parameter in bytes, including null-terminator. Yes, the null-terminator is included. Periodt. 🌱

🔥 SEE ALSO 🔥

• 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_req_uefi_set_variable(9)
• struct qsee_rsp_uefi_set_variable(9)
• struct qsee_req_uefi_get_next_variable(9)
• struct qsee_req_uefi_query_variable_info(9)
• struct qsee_rsp_uefi_query_variable_info(9)

💖 okay that's the whole page, bestie! source: ./drivers/firmware/qcom · date: October 2026 · mwah 💅✨