ENUM PS3_SYS_MANAGER_BUTTON_EVENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum ps3_sys_manager_button_event(9)

okay so this is a page straight out of the Kernel API Manual (section 9, bestie, kernel-land) and it's literally just two enum values that tell you how a button event happened. that's it. that's the whole vibe. tiny page, huge main character energy. let's go πŸŽ€


✨ NAME ✨

enum ps3_sys_manager_button_event β€” the button event payload values. yes, "payload values," plural, because there are two and we respect both of them πŸ’–


🌸 SYNOPSIS 🌸

enum ps3_sys_manager_button_event {
    PS3_SM_BUTTON_EVENT_HARD ,
    PS3_SM_BUTTON_EVENT_SOFT

};

look at her. gorgeous. two constants and a dream πŸ¦‹ (and yes, that comma after PS3_SM_BUTTON_EVENT_HARD is real, we did not touch it, we keep things exactly as they are around here, no cap)


🫢 Constants 🫢

  • PS3_SM_BUTTON_EVENT_HARD β€” the event was generated by hardware. like, the actual physical button did the thing. real-world energy. iconic πŸ”₯
  • PS3_SM_BUTTON_EVENT_SOFT β€” the event was generated by software. somebody's code went "hey what if button" and here we are. also iconic, just in a code way ✨
ngl bestie, that's genuinely the entire enum. no hidden fields, no secret defaults, no environment variables lurking in the shadows. two values. immaculate. periodt πŸ’…

🌈 SEE ALSO 🌈

the kernel file that lives here: ./drivers/ps3/ps3-sys-manager.c β€” and honestly, the whole friend group showed up for this one, so let's give them all their moment πŸ‘‘

like, that is a squad. go read them, they're all slaying in their own pages πŸ’œ


aaaand that's the page!! mwah πŸ’‹ this lil beauty comes to you from ./drivers/ps3, dated October 2026 β€” go forth and enumerate, bestie, you've got this πŸ“πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from