Anonymous user
Uniform Driver Interface: Difference between revisions
Sample udiprops.txt
| [unchecked revision] | [unchecked revision] |
m (Typos, wikilinks) |
(Sample udiprops.txt) |
||
Line 62:
The udiprops.txt file doesn't only allow for static configuration options, but is also used in the building process for UDI drivers since they do not use makefiles - not that it would be technically unfeasible. The UDI specification defines tools for building, packaging and installing UDI drivers for simplicity's sake since, unlike POSIX tools, they don't require operating systems to have any extra functionality (e.g., a VFS).
Below you can see a sample udiprops.txt:
# You will want to state the driver requirements. While "requires udi"
# always needs to be present, the others may be omitted, depending on
# the driver.
requires udi 0x101 # Unfortunately 0x101 is the only version
requires udi_bridge 0x101 # of the spec that can be implemented
# The ones below should be self-explanatory.
module example
region 0
# The two statements below are used for building only and may be omitted
# from binary distributions as they serve no purpose.
compile_options -DCMOS_BRIDGE_META=1
source_files udi_example.c
meta 1 udi_bridge # Using the Bus Bridge Metalanguage
Of course, udiprops.txt can be a lot more complex than this, I only wanted you to see what it looks like. You should check the specification for all compile options, statements and configuration options.
==Data objects==
| |||