Lines Matching refs:be
83 RapidIO interconnect specification defines features that may be used to provide
85 common services may act separately from device-specific drivers or be used by
87 which implements Ethernet-over-RapidIO interface. Because only one driver can be
88 registered for a device, all common RapidIO services have to be registered as
101 an enumeration and/or discovery routine may be called automatically or
104 RapidIO subsystem can be configured to be built as a statically linked or
116 define how any given method can be attached to available RapidIO mports:
122 (a) Statically linked enumeration and discovery process can be started
129 and are waiting for enumeration to be completed.
131 endpoint waits for enumeration to be completed. If the specified timeout
133 information. NOTE: a timed out discovery process may be restarted later using
137 (b) Statically linked enumeration and discovery process can be started by
140 endpoints have been successfully booted, an enumeration process shall be
142 completed a discovery process can be started on all remaining endpoints.
144 (c) Modular enumeration and discovery process can be started by a command from
146 process can be started by issuing a user-space command.
147 Similar to the option (b) above, an enumerator has to be started first.
149 (d) Modular enumeration and discovery process can be started by a module
150 initialization routine. In this case an enumerating module shall be loaded
158 destination ID can be assigned to a master port using various methods depending
166 one will be assigned destination ID=-1.
169 to the method shown above, the host destination ID(s) can be specified using
177 (i) if "hdid=" parameter is omitted all available mport will be assigned
183 process will be performed for it.
189 they must be loaded before enumeration/discovery process starts.
202 form a network which will be enumerated/discovered. Discovering endpoints have
203 to be started before an enumeration starts to ensure that all RapidIO
204 controllers have been initialized and are ready to be discovered. Configuration
206 a discovering endpoint will wait for enumeration to be completed.
213 enumeration/discovery start method may be difficult to use due to the
219 User-space start of enumeration and discovery can be used with built-in and
226 for that controller always will be 0.
239 This method can be configured as statically linked or loadable module.
243 This enumeration/discovery method can be started only once and does not support
265 it, a fake device ID will be assigned to configure a route to that switch.
292 a complete view of the network. The discovery process can be performed
306 A new enumeration/discovery method has to be attached to one or more mport
307 devices before an enumeration/discovery process can be started. Normally,
317 This process can be automated by specifying pre- or post- dependencies in the
338 NOTE: In the example above, one of "softdep" commands must be removed or