ps3_vuart_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ps3_vuart_read β€” The entry point for reading data from a port. 🫢

okay bestie, welcome to ps3_vuart_read(9) from the Kernel API Manual β€” section 9, where the kernel girlies live. This is the whole vibe check for reading data from a port, no cap ✨


✨ SYNOPSIS ✨

int ps3_vuart_read (struct ps3_system_bus_device *dev , void *buf ,
unsigned int bytes );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the original page literally just says -- undescribed -- πŸ’€ not even a crumb of lore.
  • buf β€” also -- undescribed -- πŸ™ˆ the mystery continues.
  • bytes β€” same energy: -- undescribed -- 😭 iconic lack of detail, honestly.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here’s the tea β˜•: this function queues data waiting at the port. If enough bytes to satisfy the request are already held in the buffer list, those bytes are dequeued and copied to the caller’s buffer.

Emptied list buffers are retiered. (yes, retiered β€” that’s the original spelling, I’m just the messenger πŸ’…)

If the request cannot be statified by bytes held in the list buffers, -EAGAIN is returned. That’s the whole plot. πŸ“


πŸ’… SEE ALSO πŸ’…

The whole squad, in original order, because we do not skip the boring parts in this house πŸ‘‘


byeeee bestie πŸ’œ source/version is ./drivers/ps3, dated October 2026, and this was ps3_vuart_read(9) signing off 🫢✨

πŸ“¦ where this page comes from