Lines Matching refs:of

5 gateware. As such, it is expected to be independent of the carrier
6 being used: it will perform I/O accesses only by means of
9 The matching between device and driver is based on the content of the
15 FPGA registers, by means of the `fpga_base' field of the device
18 by means of Etherbone), the `fpga_base' pointer will be NULL.
26 which is the current carrier and make use of the `carrier_data'
30 their own carriers.  An example use of carrier names is in GPIO setup
41 which it is able to drive.  This is usually done by means of a device
42 table, but in FMC we can match hardware based either on the contents of
44 Therefore, we have two tables of identifiers.
46 Matching of FRU information depends on two names, the manufacturer (or
56 identified by an array of cores (it matches if all of the cores are
59 driver, and thus the driver specifies and array of such arrays.
61 The complete set of involved data structures is thus the following:
78 Most of the FMC drivers need the same set of kernel parameters. This
79 package includes support to implement common parameters by means of
88 This is the list of parameters that are common to several modules to
92      This is an array of integers, listing carrier-specific
99      The argument is an array of strings. If no busid= is specified,
100      the first string of gateware= is used for all cards; otherwise the
106      internal structure by means of kernel messages. It is disabled by
122 Please note that not all sub-modules support all of those parameters.