STRUCT CC1352_BOOTLOADER_CRC32_CMD_DATA(9)
π NAME
struct cc1352_bootloader_crc32_cmd_data β okay bestie, this is the CC1352 Bootloader COMMAND_CRC32 request data β¨ like, it's the little struct that carries everything you need to ask the bootloader to crunch a CRC32 for you π
πΈ SYNOPSIS
struct cc1352_bootloader_crc32_cmd_data {
__be32 addr;
__be32 size;
__be32 read_repeat;
};
That's it. Three fields, all __be32 (big-endian, no cap), and honestly it's giving "small but mighty" π₯
π Members
addrβ the address where crc32 calculation starts πΊοΈ like, where the whole thing kicks off, literally the starting point of the vibe checksizeβ number of bytes comprised by crc32 calculation π so this is how many bytes get swept into the crc32, bestie, that's the whole spanread_repeatβ number of read repeats for each data location π how many times each data location gets read, fr fr
π none of these are optional-ish to explain away β they're all just __be32 fields, so keep an eye on your endianness, iykyk
π¦ SEE ALSO
Kernel file ./drivers/greybus/gb-beagleplay.cstruct gb_beagleplay(9)struct hdlc_payload(9)struct hdlc_greybus_frame(9)enum cc1352_bootloader_cmd(9)enum cc1352_bootloader_status(9)struct cc1352_bootloader_packet(9)struct cc1352_bootloader_download_cmd_data(9)hdlc_write(9)hdlc_append(9)hdlc_encoded_length(9)hdlc_tx_frames(9)csum8(9)cc1352_bootloader_pkt_rx(9)gb_message_send(9)cc1352_bootloader_empty_pkt(9)
Like, go read the whole friend group, they all hang out together in ./drivers/greybus π«Άπ
mwah π this page lives in ./drivers/greybus, dated October 2026, and it's filed under struct cc13...c32_cmd_data(9) in the Kernel API Manual β slay, go calculate some crc32s bestie πβ
π¦ 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