ps3_vuart_write(9)
okay so welcome to ps3_vuart_write(9) β yes bestie, that's the title, and this page lives in the Kernel API Manual π
β¨ NAME β¨
ps3_vuart_write β the entry point for writing data to a port. That's the whole name vibe, periodt π
π SYNOPSIS π
int ps3_vuart_write (struct ps3_system_bus_device *dev , const void *buf
, unsigned int bytes );
π ARGUMENTS π
devβ the actualstruct ps3_system_bus_deviceinstance, no cap πbufβ the manpage literally says-- undescribed --π so we're not inventing lore here, bestiebytesβ same situation:-- undescribed --π that's all the source gives us
π¦ DESCRIPTION π¦
okay so here's the vibe check: if the port is idle on entry, as much of the incoming data is written to the port as the port will accept. slay β¨
otherwise, a list buffer is created and any remaining incoming data is copied to that buffer. then the buffer is enqueued for transmission via the transmit interrupt. that's the flow, fr fr π
π₯ SEE ALSO π₯
- Kernel file
./drivers/ps3/ps3-vuart.cβ the whole thing lives here, iykyk π«Ά struct ps3_vuart_port_priv(9)struct ports_bmp(9)ps3_vuart_set_interrupt_mask(9)ps3_vuart_raw_write(9)ps3_vuart_raw_read(9)ps3_vuart_clear_rx_bytes(9)struct list_buffer(9)ps3_vuart_queue_rx_bytes(9)ps3_vuart_read(9)ps3_vuart_work(9)ps3_vuart_handle_interrupt_tx(9)ps3_vuart_handle_interrupt_rx(9)ps3_vuart_handle_port_interrupt(9)ps3_vuart_irq_handler(9)ps3_vuart_cleanup(9)ps3_vuart_remove(9)ps3_vuart_shutdown(9)ps3_vuart_port_driver_register(9)ps3_vuart_port_driver_unregister(9)
muah π β source/version footer is ./drivers/ps3, dated October 2026, and this page is still repping ps3_vuart_write(9). byeee π«Ά
π¦ 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