Lines Matching refs:with

9 trying to come up with a unified interface to manage the execution units and
29  * Only use fixed sized integers. To avoid conflicts with typedefs in userspace
61  * Have a plan for extending ioctls with new flags or new fields at the end of
71    an ioctl struct with random stack garbage in the yet unused parts. Which
78 Fun with Error Paths
88    example is sprite positioning values fed directly into the hardware with the
90    server doesn't bother with clamping itself and the cursor wraps around the
102    interrupting your main test suite constantly with signals. Thanks to X's
104    paths pretty much for free for graphics drivers. Also, be consistent with
106    userspace library. The i915 driver botched this with the set_tiling ioctl,
107    now we're stuck forever with some arcane semantics in both the kernel and
153  * Consider ditching any synchronous wait ioctls with timeouts and just deliver
179    explictly. Only go with a more global per-device namespace if the objects
181    that the per-device modeset objects like connectors share a namespace with
209    per-device settings, or for child objects with fairly static lifetimes (like
210    output connectors in drm with all the detection override attributes). Or
211    maybe only your testsuite needs this interface, and then debugfs with its
216 be stuck with a given ioctl essentially forever. You can try to deprecate