nci_recv_frame(9)
okay so this is nci_recv_frame(9) from the Kernel API Manual, and its whole vibe is receiving a frame from NCI drivers, no cap. It returns an int, and it takes two arguments β both are kind of the main characters here π
.
π NAME π
nci_recv_frame β receive frame from NCI drivers. That's the assignment, bestie, and it ate β¨.
π¦ SYNOPSIS π¦
The signature is staying exactly like this, character for character, because we do not mess with code on this page:
int nci_recv_frame (struct nci_dev *ndev , struct sk_buff *skb );
π ARGUMENTS π
Two args, two icons, okay?
ndevβ the NCI device. Like, the device struct you're handing in π«Ά.skbβ thesk_buffto receive. It's the buffer coming through, literally the whole point π.
π SEE ALSO π
- Kernel file:
./net/nfc/nci/core.cβ go look at the source, iykyk. - The bestie functions:
nci_allocate_device(9),nci_free_device(9),nci_register_device(9),nci_unregister_device(9)β all linked up and ready for your reading era π.
mwah π β cute sign-off time: source/version is ./net/nfc/nci, the date is October 2026, and the page is nci_recv_frame(9), bestie π«Άπ
π¦ 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