hdlc_write(9)
π NAME π
okay so bestie, we're in the Kernel API Manual and the main character is hdlc_write(9). Its name line says: Consume HDLC Buffer. That's the whole assignment, and it ate. π
β¨
β¨ SYNOPSIS β¨
void hdlc_write (struct gb_beagleplay *bg );
No cap, that's the signature exactly as the page gives it. π«Ά
π«Ά ARGUMENTS π«Ά
bgβ beagleplay greybus driver. That's the argument, that's the one-liner, and yes we're keeping it cute but exact. π
π DESCRIPTION π
Short and lowkey important: Assumes that consumer lock has been acquired. So the vibe check is that the consumer lock has to have been acquired already β that's the assumption the page lays out. Periodt. πβ¨
π SEE ALSO π
The kernel file ./drivers/greybus/gb-beagleplay.c is the home base, and here's the whole friend group of references β all of them, no skips, fr fr:
struct 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)struct cc1352_bootloader_crc32_cmd_data(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)
okay bye bestie β this page's source is ./drivers/greybus, the version/date moment is October 2026, and the manual page is hdlc_write(9). mwah πππ¦
π¦ 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