vcc_probe(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 vcc_probe(9) 🎀

okay so bestie, this is the Kernel API Manual page for vcc_probe, and the vibe check is: it gets a VCC port initialized. no cap, that’s the main character energy here 💖

✨ NAME ✨

vcc_probe — Initialize VCC port. literally the whole name-and-purpose situation, periodt.

🌸 SYNOPSIS 🌸

int vcc_probe (struct vio_dev *vdev , const struct vio_device_id *id );

🦋 ARGUMENTS 🦋

  • vdev — Pointer to VIO device of the new VCC port. like, the device pointer for the fresh VCC port, bestie.
  • id — VIO device ID. the identifier situation for that VIO device, yep.

💅 DESCRIPTION 💅

okay so here’s what vcc_probe is doing, fr fr:

  • It initializes a VCC port to receive serial console data from the guest domain.
  • It sets up a TTY end point on the control domain.
  • It sets up VIO/LDC link between the guest & control domain endpoints.

that’s the whole setup arc: port initialized for that serial console data, TTY end point on the control domain, and the link between the guest & control domain endpoints. no extra assumptions, just what the page says 💜

👑 RETURN 👑

Returns the status of the probe. that’s the return value, bestie — no secret bonus lore 🙈

🌈 SEE ALSO 🌈

Kernel file: ./drivers/tty/vcc.c

okay bestie, that’s the whole page! the footer source/version is ./drivers/tty, the date is October 2026, and the page is vcc_probe(9) — mwah, slay 💋✨

📦 where this page comes from