IEEE1284_SET_TIMEOUT(3)

✨ IEEE1284_SET_TIMEOUT ✨

okay bestie, we're in section 3 of the Functions manual, and today's main character is ieee1284_set_timeout 💅

---

🌸 NAME 🌸

ieee1284_set_timeout — modify inactivity timeout

---

🎀 SYNOPSIS 🎀

#include <ieee1284.h>

struct timeval *ieee1284_set_timeout(struct parport *port,
                                     struct timeval *timeout);

---

🦋 DESCRIPTION 🦋

So this function sets a brand new value for the inactivity timeout — the one that block transfer functions use — and then hands you back the old value. it's giving "new one in, old one out" 🔥

The port must be claimed. no claim, no service, periodt.

And listen — the timeout parameter can be NULL, and if it is, the old value just stays exactly as it was, untouched, unbothered, minding its own business 🙈

---

💖 RETURN VALUE 💖

This function returns a pointer to a struct timeval that represents the old value. and here's the tea: it uses the same storage as the port structure, so it is not valid after closing the port. like, do not go using that pointer after you close the port, bestie, it will not end well 💀

---

🌈 NOTES 🌈

Note that this is an inactivity time-out, not an absolute time-out. big difference, iykyk.

During a data transfer, if the peripheral is inactive for the length of time specified, then the host gives up. that's it, that's the vibe check. ⭐

Also it's advisory — no guarantee is made that the transfer will ever complete. so like, lowkey it might just... never finish. no cap. 😭

---

👑 AUTHOR 👑

Tim Waugh <twaugh@redhat.com>

• Author.

---

💜 COPYRIGHT 💜

Copyright © 2001-2003 Tim Waugh

---

and that's the whole page, bestie!! 🫶 this was the IEEE1284_SET_TIMEOUT(3) page, dated 09/18/2007, from the Functions manual — slay, ate, no crumbs left, mwah 💅✨🎀