UEP(4)

✨ UEP ✨ β€” the eGalax touchscreen driver, bestie edition πŸ’…

okay so you found the uep page in the Kernel Interfaces Manual and honestly? slay. it's giving "I want my touchscreen to work on FreeBSD" and we're gonna get you there. no cap.


🌸 SYNOPSIS 🌸

want this driver baked right into your kernel? drop these lines into your kernel configuration file, bestie:

device uep
device usb

or, if you'd rather be a module girlie and load it at boot time, put this line in loader.conf(5):

uep_load="YES"

and if you want it compiled with evdev support turned on, add these:

options EVDEV_SUPPORT
device evdev

πŸ’– DESCRIPTION πŸ’–

the uep driver is the whole support system for eGalax onscreen touch panels. periodt.

here's the tea though β€” the driver is a stub. it literally just probes and attaches to the USB device, creates a device entry, and then feeds reassembled packets from the hardware into it. that's it, that's the job. depending on which compile-time kernel options you chose, it supports either native or evdev operation modes.

want your mouse/touch working in X(7) in native mode? install ports/x11-drivers/xf86-input-egalax. πŸŽ€

want it working in X(7) in evdev mode? install ports/x11-drivers/xf86-input-evdev instead. πŸ¦‹


🌈 FILES 🌈

uep creates a blocking pseudo-device file β€” she's a real one. you get:

  • /dev/uep0 β€” in native mode
  • /dev/input/eventN β€” in evdev mode

πŸ‘‘ SEE ALSO πŸ‘‘

go read these, iykyk:


🫢 AUTHORS 🫢

the uep driver was written by Gleb Smirnoff <glebius@FreeBSD.org>. legend behavior, honestly.


πŸ’€ BUGS πŸ’€

uep cannot act like sysmouse(4), because sysmouse(4) does not support absolute motion events. that's just how it is, bestie. no workaround listed, so don't come for me. 😭

and that's the whole page, fr fr. this one's from Debian, dated August 5, 2018 β€” so if you're reading this years later, just know she's been iconic since then. πŸ’œβœ¨ bye bestie, go touch something (with a supported panel, obviously). 🌸

πŸ“¦ where this page comes from