Jump to content

CONFIG.SYS PSD Statements: Difference between revisions

From EDM2
No edit summary
Ak120 (talk | contribs)
mNo edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[The Config.sys Documentation Project|Return to The Config.sys Documentation Project Main Page]]
{{CFGProject}}
 
PSD stands for "Platform Specific Driver". These drivers provide an abstraction layer for the underlying hardware by allowing the operating system to call generic functions to perform platform-specific operations without worrying about the actual hardware implementation.
PSD stands for "PLATFORM SPECIFIC DRIVERS". These drivers provide an abstraction layer for the underlying hardware by allowing the operating system to call generic functions to perform platform -specific operations without worrying about the actual hardware implementation.


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.
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.
Line 7: Line 6:
PSD statements are processed before BASEDEV, IFS, and DEVICE statements.  
PSD statements are processed before BASEDEV, IFS, and DEVICE statements.  


=PSD=ACPI.PSD=
*[[ACPI.PSD]] - ACPI platform-specific driver
 
ACPI interface for developers.
 
  psd=acpi.psd <parameters>
 
'''Parameters'''
 
* /SMP
activate multi-processor support
 
* /B:name:number
Bus - make the bus %name% with %bus number% work in APIC mode else it remains in PIC mode.
In other words, inform all devices on bus %name%, that they are working in APIC mode. If using ACPI snooper then /B is not needed.
 
* /Onumber
Output - The number of COM-port used for debug output  (values: 1, 2, address of I/O port)
It is suitable for debug version of acpi.psd. Configure receiver: 115200,8,n HW flow contol
                   
* /LS:number
Leave Sleep - after sleep state the computer will be switched to this state (0 - no switch, 5 - turn off)
 
* /PIC               
* /APIC         
Multiprocessor support can run in 2 modes: PIC or APIC. PIC is default, Use /PIC to activate 8259 PIC instead of APIC.
    * PIC is good enough
    * APIC is better but doesn't work on some computers and requires extra efforts to setup computer.
 
* /CST:name     
name of method responsible for _CST method.
Example: /CST:XCST. You can find the method in the subtree  of CPU. (It's Cx state). It is needed for APM, idle of CPU,etc
               
* /AFS
By default ACPI is started from ACPI.PSD. Use this switch  to start ACPI from snooper. Use it if using ACPI snooper. Usually you need this if loading ACPI table via snooper.
This switch has no effect if using SMP.
 
* /IRQ:x
Experimental switch (specially for Acer Ferrari notebook) Allows replace ACPI IRQ number 
 
* /NOD         
(Enabled by default) Experimental switch to activate internal OEMHLP$ driver disable acpica.add if using this switch. APIC mode may work bad without this switch.
               
* /!NOD         
Disable internal OEMHLP$ driver. Don't forget activate acpica.add (read troubleshooting.doc)
 
 
* /R           
Use ACPI Reset instead of kernel's reset. It is useful if running SMP kernel only. Use it if have troubles with system reboot or shutdown.
               
* /FS           
"Full Safe"  - use this key for Dell notebooks
 
* /EIS         
"Enable Intel Slack", AcpiGbl_EnableInterpreterSlack 
The Intel interpreter strictly follows the ACPI specification. 
Setting this switch allows the interpreter to ignore certain errors and/or bad AML constructs.
 
 
Use it if ACPI log contains errors messages.
This switches are useful for APIC mode only:
 
* /CD
"Crazy Device"  - use this switch if USB doesn't work
 
* /TMR         
Use it if running SMP machine and the motherboard doesn't follow MPS 1.4 standard.
               
* /DV:vector   
Dummy Vector - hide the vector. The kernel will not process it.
(/DV:0x57 is enabled by default on every PC now)
 
* /Q
Quiet mode. It does not show any message on normal boot.
   
'''Notes:'''
*) All digital values are accepted in hex or decimal form:
    0x??? (hex)
    0??  (octal)
    ???  (decimal)
 
 
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|No
|No
|No
|No
|Yes
|Yes
|}
 
 
=PSD=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
==ALR.PSD==
indicates that the system should be configured for processors where is a decimal number (ie 5, 8, 12).
Advanced Logic Research (ALR)
PSD=ALR.PSD


* /nmi
==CAVERUN.PSD==
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.
IBM PC Server 720
PSD=CAVERUN.PSD


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.
*[[OS2APIC.PSD]]


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).
* [[OS2PCAT.PSD]]


* /pic
==OS4APIC.PSD==
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.
This is a component part of the OS/4 Kernel project.  


* /prec
'''Parameters:'''
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.


There are three (3) possible entries that can describe a route:
* /APIC
* route to the I/O APIC
To route IRQ through IOAPIC. Use the /APIC option switch only when PRELOAD is set in the os2ldr.ini file. If this switch is not used then the PIC mode is set and the IRQ will be routed through PIC.
* 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.
==PROLIANT.PSD==
Compaq Proliant 2X00 or Proliant 4X00 Server
PSD=PROLIANT.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.
==TRICRD.PSD==
Tricord
PSD=TRICRD.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.
==V1_EBI2.PSD==
PSD=V1_EBI2.PSD


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.
==VIPERMP.PSD==
PSD=VIPERMP.PSD


'''NOTE:''' The arguments to the PSD are NOT case sensitive.  
==WYSE.PSD==
Wyse
PSD=WYSE.PSD


'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|No
|No
|No
|Yes
|Yes
|Yes
|}
[[Category: The Config.sys Documentation Project]]
[[Category: The Config.sys Documentation Project]]

Latest revision as of 22:44, 19 February 2020

The Config.sys Documentation Project
  1. BASEDEV Statements
  2. CALL Statements
  3. DEVICE Statements
  4. IFS Statements
  5. OS/2 Commands
  6. DOS Commands
  7. RUN Statements
  8. SET Statements
  9. PSD Statements
  10. Other Information
  1. Programs
  2. Hardware
  3. List of Statements

PSD stands for "Platform Specific Driver". These drivers provide an abstraction layer for the underlying hardware by allowing the operating system to call generic functions to perform platform-specific operations without worrying about the actual hardware implementation.

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.

  • ACPI.PSD - ACPI platform-specific driver

ALR.PSD

Advanced Logic Research (ALR)

PSD=ALR.PSD

CAVERUN.PSD

IBM PC Server 720

PSD=CAVERUN.PSD

OS4APIC.PSD

This is a component part of the OS/4 Kernel project.

Parameters:

  • /APIC

To route IRQ through IOAPIC. Use the /APIC option switch only when PRELOAD is set in the os2ldr.ini file. If this switch is not used then the PIC mode is set and the IRQ will be routed through PIC.

PROLIANT.PSD

Compaq Proliant 2X00 or Proliant 4X00 Server

PSD=PROLIANT.PSD

TRICRD.PSD

Tricord

PSD=TRICRD.PSD

V1_EBI2.PSD

PSD=V1_EBI2.PSD

VIPERMP.PSD

PSD=VIPERMP.PSD

WYSE.PSD

Wyse

PSD=WYSE.PSD