Lines Matching refs:the

7 If the gameport doesn't provide more than the inb()/outb() functionality,
8 the code needed to register it with the joystick drivers is simple:
16 gameport generic code will take care of the rest.
19 choose which one to program the hardware to, starting from the more exotic
20 addresses is preferred, because the likelihood of clashing with the standard
24 0x218 would be the address of first choice.
27 space (is above 0x1000), use that one, and don't map the ISA mirror.
29 Also, always request_region() on the whole io space occupied by the
30 gameport. Although only one ioport is really used, the gameport usually
31 occupies from one to sixteen addresses in the io space.
33 Please also consider enabling the gameport on the card in the ->open()
34 callback if the io is mapped to ISA space - this way it'll occupy the io
35 space only when something really is using it. Disable it again in the
36 ->close() callback. You also can select the io address in the ->open()
37 callback, so that it doesn't fail if some of the possible addresses are
66 There are gameports that can report the axis values as numbers, that means
67 the driver doesn't have to measure them the old way - an ADC is built into
68 the gameport. To register a cooked gameport:
91 The only confusing thing here is the fuzz value. Best determined by
92 experimentation, it is the amount of noise in the ADC data. Perfect
94 See analog.c and input.c for handling of fuzz - the fuzz value determines
95 the size of a gaussian filter window that is used to eliminate the noise
96 in the data.
104 more than one gameport instance simultaneously, use the ->private member of
105 the gameport struct to point to your data.
121 A private pointer for free use in the gameport driver. (Not the joystick
126 Number assigned to the gameport when registered. Informational purpose only.
135 Raw mode speed of the gameport reads in thousands of reads per second.
139 If the gameport supports cooked mode, this should be set to a value that
140 represents the amount of noise in the data. See section 3.
144 Trigger. This function should trigger the ns558 oneshots. If set to NULL,
149 Read the buttons and ns558 oneshot bits. If set to NULL, inb(io) will be
154 If the gameport supports cooked mode, it should point this to its cooked
155 read function. It should fill axes[0..3] with four values of the joystick axes
156 and buttons[0] with four bits representing the buttons.
160 Function for calibrating the ADC hardware. When called, axes[0..3] should be
161 pre-filled by cooked data by the caller, max[0..3] should be pre-filled with
162 expected maximums for each axis. The calibrate() function should set the
163 sensitivity of the ADC hardware so that the maximums fit in its range and
164 recompute the axes[] values to match the new sensitivity or re-read them from
165 the hardware so that they give valid values. 
169 Open() serves two purposes. First a driver either opens the port in raw or
170 in cooked mode, the open() callback can decide which modes are supported.
172 here. Prior to this call, other fields of the gameport struct (namely the io
177 Close() should free the resources allocated by open, possibly disabling the
183 For internal use by the gameport layer.