OS2APIC.PSD

In Warp Server for e-business SMP, all the platform specific code from the operating system is removed, and placed it into platform specific drivers. These drivers provide an abstraction layer for the underlying hardware by allowing the OS to call generic functions to perform platform specific operations without worrying about the actual hardware implementation. This allows to support new platforms without modifying the operating system.

PSD's are specified in CONFIG.SYS by using the PSD keyword, and must conform to the 8.3 file naming convention (e.g. PSD=BELIZE.PSD). They cannot contain either drive, or path information because OS/2 cannot process such information at the stage of the startup sequence when the PSD statements are processed. The root directory of the startup partition is first searched for the specified file name, then the \OS2 directory of the startup partition. If drive or path information is included in a PSD statement, an error is generated.

PSD parameters may be specified after the PSD's name, and may be a maximum of 1024 characters long. The parameter string is not interpreted, or parsed by OS/2, it is passed verbatim, as an ASCIIZ string when the PSD's Install function is invoked.

If multiple PSD statements are encountered. OS/2 will load each PSD in the order listed in CONFIG.SYS, and call the PSD's install function. The first PSD which successfully installs, will be the one OS/2 uses.

PSD statements are processed before BASEDEV, IFS, and DEVICE statements.

Please note that any time you add or make changes to the CONFIG.SYS file, you must restart the system in order for the changes to become effective. The CONFIG.SYS file is read only during system startup. Anything added to this file after system initialization does not work until you restart the system.

Parameter:
 * /apic - indicates that the PSD should enable symetric interrupt mode.
 * /p - indicates that the system should be configured for processors where is a decimal number (ie 5, 8, 12).
 * /nmi - indicates to the system a default signal route for NMIs. This allows the route to be specified for NMIs if there isn't one defined by the MP configuration tables set up by BIOS.

By using the /prec option (see below), it is possible to override what is in the MP configuration tables in the event that they have been built incorrectly by the BIOS.

The argument is "int" or "lint". The first case indicates the interrupt pin number to which the NMI signal is wired on the I/O apic. The second case indicates the interrupt poin number to which the NMI signal is wired on the local apic. is a decimal number (ie 0, 3, 12).

indicates to the system a default signal route for the 8259 interrupt controller when the system is running in "virtual wire" mode. This allows the route to be specified for the interrupt controller if there isn't one defined by the MP configuration tables set up by BIOS. By using the /prec option (see below), it is possbile to override what is in the MP configuration tables in the event that they have been built incorrectly by the BIOS.
 * /pic

indicates to the system the precedence order to be used in determining the routing for the NMI signal and the interrupt signal from the interrupt controller. This allows control over the choosing of a routing entry when there is more than one entry.
 * /prec

There are three (3) possible entries that can describe a route:
 * route to the I/O APIC
 * route to the Local APIC
 * route described by argument(s) to the PSD

The first two may be specified in the MP configuration tables that are built by the BIOS. The third may be specified on the argument line to the PSD.

Each type of route is described by one letter. "i" for the I/O APIC routes, "l" for the local APIC routes, and "d" for the routes described by the argument line to the PSD.

The precedence string is *exactly* 3 characters long. The first character indicates the type of routes to be considered first, the second indicates the routes to be considered next and the third indicates the routes that are to be considered last.

As an example, "ild" indicates that I/O APIC routes are to considered first, followed by local APIC routes and finally routes specified on the argument line. In contrast, "dil" indicates that routes on the argument line are to be considered first, then the I/O APIC and finally the local APIC.

NOTE: The arguments to the PSD are NOT case sensitive.