- Timestamp:
- 04/17/15 14:46:08 (9 years ago)
- Branches:
- 4.11, 5, master
- Children:
- 491434cd
- Parents:
- c5d86ec0
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user/libpci.t
rc5d86ec0 r3985e758 1 1 @c 2 @c COPYRIGHT (c) 2011 2 @c COPYRIGHT (c) 2011,2015 3 3 @c Aeroflex Gaisler AB 4 4 @c All rights reserved. … … 30 30 macros in confdefs.h. It is also possible to enable PCI_LIB_NONE (No 31 31 Configuration) which can be used for debuging PCI access functions. 32 32 33 @itemize @bullet 33 34 @item Auto Configuration (do Plug & Play) … … 98 99 @subsection PCI Configuration 99 100 100 During start up the PCI bus must be configured in order for host and peripherals 101 to access one another using Memory or I/O accesses and that interrupts are 102 properly handled. Three different spaces are defined and mapped separately: 101 During start up the PCI bus must be configured in order for host and 102 peripherals to access one another using Memory or I/O accesses and that 103 interrupts are properly handled. Three different spaces are defined and 104 mapped separately: 105 103 106 @enumerate 104 107 @item I/O space (IO) … … 118 121 In order to support different configuration methods the following configuration 119 122 libraries are selectable by the user: 123 120 124 @itemize @bullet 121 125 @item Auto Configuration (run Plug & Play software) 122 126 @item Read Configuration (relies on a boot loader or BIOS) 123 127 @item Static Configuration (write user defined setup, no Plug & Play) 124 @item Peripheral Configuration (user defined setup, no access to configuration space) 128 @item Peripheral Configuration (user defined setup, no access to 129 configuration space) 125 130 @end itemize 126 131 … … 140 145 The active configuration method can be selected at compile time in the same 141 146 way as other project parameters by including rtems/confdefs.h and setting 147 142 148 @itemize @bullet 143 149 @item CONFIGURE_INIT … … 147 153 148 154 See the RTEMS configuration section how to setup the PCI library. 149 150 155 151 156 @subsubsection Auto Configuration … … 165 170 166 171 The auto configuration routines support: 172 167 173 @itemize @bullet 168 174 @item PCI 2.3 … … 179 185 180 186 Not supported: 187 181 188 @itemize @bullet 182 189 @item hot-pluggable devices … … 189 196 address range, in order to support this the host driver or BSP must make sure 190 197 that I/O addresses region is within this region. 191 192 198 193 199 @subsubsection Read Configuration … … 200 206 the auto or read configuration approaches. 201 207 202 203 208 @subsubsection Static Configuration 204 209 … … 215 220 tree named pci_hb. 216 221 217 218 222 @subsubsection Peripheral Configuration 219 223 … … 224 228 on the same bus or at another PCI bus. 225 229 226 A PCI peripheral is not allowed to do PCI configuration cycles, which means that227 it must either rely on the host to give it the addresses it needs, or that the 228 addresses are predefined.230 A PCI peripheral is not allowed to do PCI configuration cycles, which 231 means that it must either rely on the host to give it the addresses it 232 needs, or that the addresses are predefined. 229 233 230 234 This configuration approach is very similar to the static option, however the … … 238 242 configuration software, etc. in order to access different regions in a way 239 243 not dependent upon the host driver, BSP or platform. 244 240 245 @itemize @bullet 241 246 @item PCI configuration space … … 289 294 given to the functions is not the PCI I/O addresses, the caller must have 290 295 translated PCI I/O addresses (available in the PCI BARs) into a BSP or host 291 driver custom address, see @ref{ Access functions} for how addresses are292 translated.296 driver custom address, see @ref{PCI Library Access functions} for how 297 addresses are translated. 293 298 294 299 @example … … 382 387 @end example 383 388 384 385 389 @subsection PCI Interrupt 386 390 … … 402 406 use the standard RTEMS interrupt functions directly. 403 407 404 405 408 @subsection PCI Shell command 406 409
Note: See TracChangeset
for help on using the changeset viewer.