STRUCT EC_PARAMS_READ_MEMMAP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct ec_params_read_memmap(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so you found your way into the Kernel API Manual (struct ec_params_read_memmap(9)) and honestly? iconic of you. this is a kernel struct page, it's giving "small but does exactly one job" energy, and we're gonna read it together. no cap. ✨


🌸 NAME 🌸

struct ec_params_read_memmap β€” the parameters for the read memory map command. that's it, that's the whole vibe. it's the little envelope of params you hand over when you wanna read the memory map. 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

struct ec_params_read_memmap {
    uint8_t offset;
    uint8_t size;
 };

look at her. two fields. two uint8_ts. absolutely no notes. πŸ’–


πŸ‘‘ Members πŸ‘‘

  • offset β€” where in the memmap you're starting from, and bestie it's an offset in memmap β€” specifically one of the EC_MEMMAP_* constants, okurrr. that's the address space you're poking at. πŸ“
  • size β€” how many bytes you want to read. literally just "how much, in bytes." that's the whole thing. πŸ“
ngl there are only two members here so this section is short and sweet β€” but don't let anybody tell you small structs don't matter, because they ate. πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

the way this SEE ALSO section is long β€” grab a snack, bestie, we're going on a tour of the whole family. 🧚

  • the kernel file itself, king of the source of truth: ./include/linux/platform_data/cros_ec_commands.h
  • struct ec_lpc_host_args(9)
  • struct ec_host_request(9)
  • struct ec_host_response(9)
  • struct ec_response_proto_version(9)
  • struct ec_params_hello(9)
  • struct ec_response_hello(9)
  • struct ec_response_get_version(9)
  • struct ec_params_read_test(9)
  • struct ec_response_read_test(9)
  • struct ec_response_get_chip_info(9)
  • struct ec_response_board_version(9)
  • struct ec_params_get_cmd_versions(9)
  • struct ec_params_get_cmd_versions_v1(9)
  • struct ec_response_get_cmd_versions(9)
  • struct ec_response_get_comms_status(9)
  • struct ec_response_get_protocol_info(9)
  • struct ec_response_flash_info(9)
  • struct ec_response_flash_info_1(9)
  • struct ec_params_flash_read(9)
  • struct ec_params_flash_write(9)
  • struct ec_params_flash_erase(9)
  • struct ec_params_flash_erase_v1(9)
  • struct ec_params_flash_protect(9)
  • struct ec_response_flash_protect(9)
  • struct ec_params_flash_region_info(9)
  • struct ec_params_flash_select(9)
  • struct ec_params_cec_write(9)
  • struct ec_params_cec_write_v1(9)
  • struct ec_params_cec_read(9)
  • struct ec_response_cec_read(9)
  • struct ec_params_cec_set(9)
  • struct ec_params_cec_get(9)
  • struct ec_response_cec_get(9)
  • struct ec_response_cec_port_count(9)
  • struct ec_params_battery_static_info(9)
  • struct ec_response_battery_static_info(9)
  • struct ec_params_battery_dynamic_info(9)
  • struct ec_response_battery_dynamic_info(9)
  • struct ec_params_charger_control(9)

like, the whole friend group showed up. main character energy collectively. πŸ’œ


πŸ’€ friendly reminder that we do not make stuff up on this page β€” everything above is exactly what the manpage says, just with better vibes. iykyk.

and that's the page, bestie!! πŸŽ€ this one came to you from ./include/linux/platform_data and it's dated October 2026 β€” so consider this your cute little sign-off, mwah, go read some kernel headers, slay. πŸŒˆβœ¨πŸ’–

πŸ“¦ where this page comes from