flink_linux
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| flink_linux [2023/12/19 16:08] – [Module Parameters] ursgraf | flink_linux [2023/12/19 16:10] (current) – [Module Parameters] ursgraf | ||
|---|---|---|---|
| Line 46: | Line 46: | ||
| | mpc5200/ | | mpc5200/ | ||
| | imx6/ | | imx6/ | ||
| - | | arm/ | + | | zynq/ |
| Busses like //PCI// have discoverability built into them. Any device connected to such a bus can tell the system, what kind of device it is and what resources it uses. On the //SPI// this is not possible. Therefore, you must provide the total device memory length when loading the module. This length is determined by the number and types of the subdevices implemented in VHDL, see [[flink_vhdl|flink VHDL]]. \\ If an //info subdevice// is present, it will give the information about the total device size and the parameter can be ommitted, see [[flink_vhdl# | Busses like //PCI// have discoverability built into them. Any device connected to such a bus can tell the system, what kind of device it is and what resources it uses. On the //SPI// this is not possible. Therefore, you must provide the total device memory length when loading the module. This length is determined by the number and types of the subdevices implemented in VHDL, see [[flink_vhdl|flink VHDL]]. \\ If an //info subdevice// is present, it will give the information about the total device size and the parameter can be ommitted, see [[flink_vhdl# | ||
flink_linux.1702998489.txt.gz · Last modified: 2023/12/19 16:08 by ursgraf
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
