Overview
Most network drivers support the following common options.
Network Driver Options
The following options can be set in loader.cfg. loader.cfg is located under %INTIMECFG%NodeName\etc\ (on INtime DIstributed RTOS the INTIMECFG variable points to the /config directory).
To edit loader.cfg for NodeA, for example, follow these steps in DOS prompt, or FTP the D-RTOS file to a host for editing:
- c:>
- cd %INTIMECFG%\NodeA\etc
- notepad loader.cfg
Note: Each node has its own loader.cfg file.
On INtime Distributed RTOS remember to copy the file back to the system after editing.
'xxx' represents the device name and the unit number (e.g. 'ie1g0').
dev.xxx.debug=n
Set debug trace flag. Debugging information is output to I/O console. The default is 0 (= no debug trace).
dev.xxx.list=0|1|2|3
1=display all devices recognized by this driver. Devices assigned to INtime are marked with a "*".
2=display the list of device IDs supported by this driver.
3=do both 1 and 2.
The default is 0 (=no list).
dev.xxx.speed=0|10|100|1000
Set communication speed. The default is 0 (= auto).
dev.xxx.duplex=auto|full|half
Set duplex mode. The default is auto.
dev.xxx.poll=n
If non zero-value is specified, then polling mode is enabled for the device. In this mode the driver polls the status register instead of relying on the interrupt from the device. The value n determines the polling interval, in Kernel ticks. The default is 0 (= polling is disabled).
dev.xxx.pollpri=n
Set the polling thread priority to n. The value is ignore if not in polling mode. The default polling priority is set by the system.
dev.xxx.macaddr=xx:xx:xx:xx:xx:xx
Change ethernet MAC address for the device.
dev.xxx.msi=default|force|no
This option applies only to the devices which are MSI (Message Signaled Interrupt) capable.
'default' =system determines which interrupt to use based on the configuration and device type.
'force' = forces use of MSI instead of legacy interrupt. Depending on the configuration and device, the device may or may not work.
'no' = don't use MSI but use the legacy interrupt. Depending on the configuration and device, the device may or may not work.
dev.xxx.intr_thread_pri=n
n = -1: (default) the priority of the interrupt thread is set by INtime kernel base on the interrupt level.
n=0..254: Explicitly specify the priority of interrupt service thread.
Requirements
Versions |
Link to |
INtime 4.0 |
netlib.lib |
See Also