fas216_send_command(9)
okay so bestie, you've landed on the fas216_send_command(9) page from the Kernel API Manual, and honestly? She's short, she's iconic, and she knows exactly what she's doing. π
πΈ NAME πΈ
fas216_send_command β send command after all message bytes have been sent.
π¦ SYNOPSIS π¦
void fas216_send_command (FAS216_Info *info );
π ARGUMENTS π
infoβ the interface which caused bus service. That's the whole argument, bestie. She's carrying theFAS216_Info *, and she's the one who caused bus service. π«Ά
β¨ DESCRIPTION β¨
Send a command to a target after all message bytes have been sent.
That's literally the assignment. The function returns void, so there's no return value to obsess over, and the timing is the main-character detail: the command goes out after all the message bytes have been sent. No cutting the line. Periodt. π
π SEE ALSO π
Kernel file: ./drivers/scsi/arm/fas216.c β that's the source file, and here's the whole squad it points you to, in order:
fas216_get_last_msg(9)fas216_syncperiod(9)fas216_set_sync(9)fas216_handlesync(9)fas216_updateptrs(9)fas216_pio(9)fas216_cleanuptransfer(9)fas216_transfer(9)fas216_stoptransfer(9)fas216_reselected_intr(9)fas216_message(9)fas216_send_messageout(9)fas216_busservice_intr(9)fas216_funcdone_intr(9)fas216_intr(9)fas216_kick(9)fas216_rq_sns_done(9)fas216_std_done(9)fas216_done(9)fas216_queue_command_internal(9)fas216_internal_done(9)fas216_eh_abort(9)fas216_eh_device_reset(9)fas216_eh_bus_reset(9)fas216_init_chip(9)fas216_eh_host_reset(9)fas216_reset_state(9)fas216_init(9)fas216_add(9)fas216_release(9)
byeee π β this page is from ./drivers/scsi/arm, dated October 2026, and it's fas216_send_command(9). Slay. π
π¦ 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