Lines Matching refs:of

6 modern devices allow relocation of such ranges, some "Legacy" VGA devices
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
19 is needed to control the sharing of these resources. This document introduces
20 the operation of the VGA arbiter implemented for the Linux kernel.
24 I.  Details and Theory of Operation
32 I. Details and Theory of Operation
38 The vgaarb is a module of the Linux Kernel. When it is initially loaded, it
40 arbiter then enables/disables the decoding on different devices of the VGA
47  open       : open user instance of the arbiter. By default, it's attached to
48               the default VGA device of the system.
52  read       : return a string indicating the status of the target like:
56               An IO state string is of the form {io,mem,io+mem,none}, mc and
65  write       : write a command to the arbiter. List of commands:
79   card_ID is of the form "PCI:domain:bus:dev.fn". It can be set to "default"
86 The driver keeps track of which user has which locks on which card. It
90 Currently, a max of 16 cards can have locks simultaneously issued from
91 user space for a given user (file descriptor instance) of the arbiter.
93 In the case of devices hot-{un,}plugged, there is a hook - pci_notify() - to
97 There is also an in-kernel API of the arbiter in case DRM, vgacon, or other
108     /* the type of resource decoded by the device */
126 decoding for that type of resource. If yes, the lock is "converted" into a
132 P2P bridges if any). In the case of vga_arb_lock(), the function will block
133 if some conflicting card is already locking one of the required resources (or
136 succeeds.  vga_arb_trylock() will return (-EBUSY) instead of blocking. Nested
140 Set the target device of this client.
150 Unlock resources of device.
156 card can be left out of the arbitration process (and can be safe to take
179 with the Xorg community in 2005 [1, 2]. In the end of 2007, Paulo Zanoni and
180 Tiago Vignatti (both of C3SL/Federal University of Paraná) proceeded his work
182 implementation of the user space side [3]. Now (2009) Tiago Vignatti and Dave