Lines Matching +full:server +full:- +full:side

7 implemented on PCI will typically have the same "hard-decoded" addresses as
8 they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994
12 The Resource Access Control (RAC) module inside the X server [0] existed for
14 than one legacy device co-exists on the same machine. But the problem happens
16 (e.g. two server in parallel). Their address assignments conflict. Moreover,
17 ideally, being a userspace application, it is not the role of the X server to
18 control bus resources. Therefore an arbitration scheme outside of the X server
23 ---------------------------
51         unplugged, we get "invalid" then for card_ID and an -ENODEV
63                 non-blocking acquire locks on target (returns EBUSY if
90 In the case of devices hot-{un,}plugged, there is a hook - pci_notify() - to
94 There is also an in-kernel API of the arbiter in case DRM, vgacon, or other
97 In-kernel interface
98 -------------------
100 .. kernel-doc:: include/linux/vgaarb.h
103 .. kernel-doc:: drivers/pci/vgaarb.c
107 ------------
139 succeeds.  vga_arb_trylock() will return (-EBUSY) instead of blocking. Nested
140 calls are supported (a per-resource counter is maintained).
173 xf86VGAArbiter (X server implementation)
174 ----------------------------------------
176 X server basically wraps all the functions that touch VGA registers somehow.
179 ----------
185 implementation of the user space side [3]. Now (2009) Tiago Vignatti and Dave
189 1) https://lists.freedesktop.org/archives/xorg/2005-March/006663.html
190 2) https://lists.freedesktop.org/archives/xorg/2005-March/006745.html
191 3) https://lists.freedesktop.org/archives/xorg/2007-October/029507.html