scm_legacy_...mmand_buffer(9)
π scm_legacy_get_command_buffer β Kernel API Manual β¨
okay so bestie, we're in the <pink>Kernel API Manual</pink> today and this page is literally about scm_legacy_get_command_buffer. Yes that is a mouthful, no I will not be shortening it, it's iconic and we respect it. π
πΈ NAME πΈ
scm_legacy_get_command_buffer β get a pointer to a command buffer. that's it. that's the whole job. she's a one-task queen π
π¦ SYNOPSIS π¦
void * scm_legacy_get_command_buffer (const struct scm_legacy_command *cmd );
not me copying this exactly because every character matters, periodt π
π ARGUMENTS π
cmdβ a command. that's the entire description she gave us. a command. okay werk, mysterious but valid π
β DESCRIPTION β
so what does she do? she returns a pointer to the command buffer of a command. that's the vibe. you hand her a command, she hands you back a pointer to that command's buffer. no cap, that's the whole plot π«Ά
bestie reminder: it says a pointer, it does not promise you anything else about it. don't go inventing guarantees, the page lowkey refuses to give more detail and we respect her boundaries π
π SEE ALSO π
go look at the kernel file ./drivers/firmware/qcom/qcom_scm-legacy.c β that's where the lore lives π
and then the whole friend group:
struct arm_smccc_args(9)struct scm_legacy_command(9)struct scm_legacy_response(9)scm_legacy_command_to_response(9)scm_legacy_get_response_buffer(9)scm_legacy_call(9)scm_legacy_call_atomic(9)
the way this is literally a whole squad and she's just the one who hands out the buffer π₯
π§ sign-off π§
this masterpiece lives in ./drivers/firmware/qcom, dated October 2026, and honestly? she ate. go get your pointer bestie, ily, drink some water ππβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms