Lines Matching +full:built +full:- +full:into
5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
33 ---------------
50 ----------
54 structure. Devices form one global device list and per-network device lists
58 ----------
68 specific switch drivers that are designed to provide hardware-specific
72 -----------
81 ------------------
83 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
87 ------------------------
91 common services may act separately from device-specific drivers or be used by
92 device-specific drivers. Example of such service provider is the RIONET driver
93 which implements Ethernet-over-RapidIO interface. Because only one driver can be
96 the same device without blocking attachment of a device-specific driver.
108 by user-space command.
110 RapidIO subsystem can be configured to be built as a statically linked or
117 ------------
132 'rio-scan.scan' for existing basic enumeration/discovery method.
140 a user-space command as it is described below (if the given endpoint was
147 started first by issuing a user-space command, after an enumeration is
152 process can be started by issuing a user-space command.
170 the command line parameter "rapidio.hdid=-1,7" will result in assignment of
172 one will be assigned destination ID=-1.
174 (b) If the RapidIO subsystem core is built as a loadable module, in addition
178 - from command line: "modprobe rapidio hdid=-1,7", or
179 - from modprobe configuration file using configuration command "options",
180 like in this example: "options rapidio hdid=-1,7". An example of modprobe
185 destination ID = -1;
188 destination ID assignments omitted from the end of list (default = -1).
190 If the host device ID for a specific master port is set to -1, the discovery
196 NOTE: If RapidIO switch-specific device drivers are built as loadable modules
199 vendor-specific callbacks on early stages.
202 ------------------------------------------------
204 Automatic enumeration/discovery start method is applicable only to built-in
207 command line parameter "rio-scan.scan=1".
224 4.3 User-space Start of Enumeration and Discovery
225 -------------------------------------------------
227 User-space start of enumeration and discovery can be used with built-in and
228 modular build configurations. For user-space controlled start RapidIO subsystem
229 creates the sysfs write-only attribute file '/sys/bus/rapidio/scan'. To initiate
231 write mport_ID (not RapidIO destination ID) into that file. The mport_ID is a
237 write '-1' (or RIO_MPORT_ANY) into the scan attribute file.
240 ----------------------------
252 unloading if it is built as a module.
254 The enumeration process traverses the network using a recursive depth-first
256 device by writing into the Host Device ID Lock CSR. It does this to ensure that
262 is written into the device's Base Device ID CSR.
267 table entry contains a pointer to a switch-specific initialization routine that
279 into device's Component Tag CSR. That unique value is used by the error
285 (0xFF for 8-bit systems and 0xFFFF for 16-bit systems) is temporarily written
286 into the routing table. The algorithm recurs by calling itself with hopcount + 1
299 devices. This way each Linux-based component of the RapidIO subsystem has
308 -------------------------------------------
321 -----------------------------------------
323 In the case when RapidIO switch drivers are built as loadable modules a user
325 This process can be automated by specifying pre- or post- dependencies in the
326 RapidIO-specific modprobe configuration file as shown in the example below.
333 options rapidio hdid=-1,2
340 # Load RapidIO switch drivers just before rio-scan enumerator module is loaded
341 softdep rio-scan pre: idt_gen2 idtcps tsi57x
343 --------------------------
362 https://www.kernel.org/doc/ols/2005/ols2005v2-pages-43-56.pdf