IRPIPE(1)

💖 IRPIPE(1) 💖

okay bestie, pull up a chair, we're talking about irpipe — a User Commands girlie from the irpipe manual. she's niche, she's powerful, and she's about to feed your kernel device some data. let's get into it ✨

---

🌸 NAME 🌸

irpipe — the tool that sends data to lircd over the /dev/irpipe kernel device. that's it, that's the job, and she does it flawlessly 💅

---

🦋 SYNOPSIS 🦋

irpipe [options] <file

irpipe --read [options] >file

irpipe --filter [options] <infile >outfile

three whole modes, one little icon 👑

---

✨ DESCRIPTION ✨

so irpipe is literally designed to feed data to lircd(8) over a /dev/irpipe device. it's your tool for getting test data into lircd in a way that's identical to real data coming off /dev/lirc devices. same vibe, same shape, no difference. fr fr.

she speaks two languages, bestie:

• text format — as defined in mode2(1)
• binary format — documented over in the lirc(4) manual page

and here's the tea: the irpipe driver lets you set the features that get returned by the LIRC_GET_FEATURES ioctl. those are all documented in lirc(4). iykyk.

⚠️ real talk: the irpipe kernel device is often not built in packaged lirc versions. if that's your situation, scroll your little eyes down to [KERNEL DRIVER] below. i got you 🫶

---

🎀 OPTIONS 🎀

• -d, --device=driver — sets the kernel device. the default is /dev/irpipe0.
• -b, --bin2text — converts binary data into text. glow up transformation ✨
• -t, --text2bin — converts text data into binary. the reverse glow up.
• -s, --add-sync — adds a long initial sync onto the converted output. this is often required for lircd to be able to decode your data, especially if the keys aren't being repeated. lowkey essential.
• -f, --filter — sends data from stdin straight to stdout. pipeline queen.
• -r, --read — sends data from the kernel device to stdout. > heads up bestie: this option is experimental and not tested. she's a risk taker, proceed accordingly 💀
• -l--length=bits — sets the kernel device signal length. this is only meaningful on LIRCCODE device emulation. don't come for me, that's just what it says.
• -F--features=bitmask — sets the features bitmask, the one returned by the LIRC_GET_FEATURES ioctl. see lirc(4) for more deets.
• -h, --help — displays the usage summary. your little cheat sheet 🌈
• -v, --version — displays the version. say hi to her ⭐

---

🧚 KERNEL DRIVER 🧚

so the irpipe tool is built to work with the irpipe kernel driver — although the --filter option works without it. that one's independent, she's fine on her own 💜

here's the catch, bestie: this driver is often not built in packaged versions. if that's the case for you, no worries, you can build the driver yourself from the sources in the drivers/irpipe directory. the catch to the catch? that requires kernel sources installed. 😭

and if you need the how-to, the drivers/irpipe/README has all the info on building and installing the driver. go read her, she's helpful 🍓

---

👑 SEE ALSO 👑

• lircd(8)
• lirc(4)

---

and that's the whole page, periodt. this little gem is irpipe 0.10.2, with a last change way back in Aug 2015 — vintage, iconic, still serving. 💖 mwah, go feed some devices 🎀✨