cti_get_port_type_fpga(9)
π cti_get_port_type_fpga β get the port type of a CTI FPGA card β¨
okay so bestie, welcome to the Kernel API Manual π we're literally about to find out what kind of port a CTI FPGA card is serving, and honestly? it's giving "one tiny helper function with main character energy" π
πΈ SYNOPSIS πΈ
enum cti_port_type cti_get_port_type_fpga (struct exar8250 *priv ,
struct pci_dev *pcidev , unsigned int port_num );
like, three args, one return, no drama π
π¦ ARGUMENTS π¦
privβ the device's private structure, aka its little inner world πpcidevβ pointer to the PCI device for this port, the actual hardware bestie π₯port_numβ which port you wanna get the type of, pick a number, any number β¨
β DESCRIPTION β
so here's the tea β β FPGA based cards port types are based on PCI IDs. that's it, that's the whole vibe. no cap π§
π RETURN π
- port type on success π
CTI_PORT_TYPE_NONEon failure π
π SEE ALSO π
- Kernel file
./drivers/tty/serial/8250/8250_exar.c struct exar8250_board(9)exar_mpio_config_output(9)_exar_mpio_set(9)cti_tristate_disable(9)cti_plx_int_enable(9)cti_read_osc_freq(9)cti_get_port_type_xr17c15x_xr17v25x(9)cti_get_port_type_xr17v35x(9)
like go read those too, they're iconic, iykyk π
lowkey reminder: failure gives you CTI_PORT_TYPE_NONE, so bestie please actually check your return value before you do anything unhinged with it π
kisses, this page lives in ./drivers/tty/serial/8250, dated October 2026, and the manual header was cti_get_port_type_fpga(9) β slay, bye π«Άπ
π¦ 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