(Page 1 of 1 in this chapter)2.2 AG Configuration File Structure 16
2.5 Configuration File Statements by AG Board 23
2.6 Creating an AG Configuration File For Your System 25
[AGBOARD] on a line by itself and ends at the end of the file or at another word or phrase in square brackets on a line by itself. Any text outside that region is ignored.
Board statement (e.g., Board n or Board All) and is terminated by any of the following:
End Board statement· Another
Board statement
[AGBOARD] section begins with a common section (starting with a Board All statement) that pertains to all the AG boards in the system, followed by sections for each AG board.
keyword = value
Interrupt keyword is in the Common section, (not the Board section)
Interrupt and ReportFile) are those intended to apply uniformly to all boards. These traditionally come at the beginning of the AGBOARD section.
DSPfile, TCP, and RunFile) are those intended to apply to a range of boards. Each range of boards requires a corresponding section. Alternatively, the boards in a range may be treated individually, with statements duplicated in each board-specific section.
Address) are those intended to apply to one specific board. These must fall within appropriate board-specific sections.
Diagnostics in the board-specific category), but it is more common to use the same level for all boards (putting it in the common category). Not all statements have this flexibility, however. In particular, Interrupt is always common and Address is always board-specific.
Interrupt statement, there must be a common section. In addition, each ISA board must have an Address statement and each PCI board must have PCIbus and PCIslot statements, so there must also be a board-specific section for each board.
Address) may occur only once for each board, others (such as DSPfile) may be repeated with different arguments for each board.
(Page 1 of 1 in this chapter)