readme.txt

isa总线设备

   3.5 Static driver configuration for Linux kernel 2.4.x and 2.6.x
       
       Note: To use static driver, you must install the linux kernel
             source package.
   
       3.5.1 Check your Linux kernel source directory. 
          For Red Hat 7.x user, you need to create link:
          # cd /usr/src
          # ln -s linux-2.4 linux

       3.5.2 Create link
	  # cd /usr/src/linux/drivers/char
	  # ln -s /moxa/mxpcdrv/driver/mxpcdrv.c mxpcdrv.c
	  # ln -s /moxa/mxpcdrv/driver/mxpcdrv.h mxpcdrv.h

       3.5.3 Modify kernel configuration file.
          Add the following line into configuration file.
	  For 2.4.x: /usr/src/linux/drivers/char/Config.in
		tristate '  MOXA SmartIO support' CONFIG_MOXA_SMARTIO
		tristate '  MOXA PC104 support' CONFIG_MOXA_PC104 <--
		...
	  For 2.6.x: /usr/src/linux/drivers/char/Kconfig
		config MOXA_SMARTIO
			tristate "Moxa SmartIO support"
			depends on SERIAL_NONSTANDARD
			...
		config MOXA_PC104			<--
			tristate "Moxa PC104 support"	<--
			depends on SERIAL_NONSTANDARD	<--

       3.5.4 Modify the kernel Makefile 
	  Add the following line into Makefile.
	  /usr/src/linux/drviers/char/Makefile

		obj-$(CONFIG_MOXA_SMARTIO) += mxser.o
		obj-$(CONFIG_MOXA_PC104) += mxpcdrv.o	<--

       3.5.5 Modify the kernel tty_init() and tty.h

	 For 2.4.x
	 /usr/src/linux/drivers/char/tty_io.c, tty_init()
		#ifdef CONFIG_MOXA_SMARTIO
			mxser_init()
		#endif
		#ifdef CONFIG_MOXA_PC104	<--
			mxpcdrv_init()		<--
		#endif				<--
		...

	 /usr/src/linux/include/linux/tty.h
		extern int mxser_init(void)
		extern int mxpcdrv_init(void)	<--	
		...


       3.5.6 Add I/O address list for PC104 Communication Modules.
          
	  In module mode, the I.O address, Vector address and IRQ 
	  number for ISA board is given by parameter. In static 
	  driver configuration, you'll have to assign it within 
	  driver's source code. If you will not install any ISA 
	  boards, you may skip to next portion.
	  The instructions to modify driver source code are as
	  below.
	  a. # cd /moxa/mxpcdrv/driver
	     # vi mxpcdrv.c

	  b. Find the array mxpcdrvBoardIO[] as below.

	     static int mxpcdrvBoardIO[]
	     = {0, 0, 0, 0};
	     static int mxpcdrvBoardIRQ[]
	     = {0, 0, 0, 0};
	     static int mxpcdrvBoardVECT[]
	     = {0, 0, 0, 0};

	  c. Change the address within this array using vi. For
	     example, to configure 2 ISA boards I/O, vector, IRQ to
	     (0x180, 0x1c0, 10) and (0x280,0x2c0, 11). Just to change
	     the source code as follows.

	     static int mxpcdrvBoardIO[]
	     = {0x180, 0x280, 0x00, 0x00};
	     static int mxpcdrvBoardVECT[]
	     = {0x1c0, 0x2c0, 0x00, 0x00};
	     static int mxpcdrvBoardIRQ[]
	     = {10, 11, 0x00, 0x00};

	  d. Repeat above three steps for Interrupt Vector Address and IRQ
	     Number, and change the value within array mxpcdrvBoardVECT[] 
	     and mxpcdrvBoardIRQ[].

       3.5.7 Setup kernel configuration
          
          Configure the kernel:

            # cd /usr/src/linux
            # make menuconfig
            
          You will go into a menu-driven system. Please select [Character
          devices][Non-standard serial port support], enable the [Moxa 
          PC104 support] driver with "[*]" by pressing space bar for built-in
	  (not "[M]"), then select [Exit] to exit this program. 
          
       3.5.8 Rebuild kernel
      	  The following are for Linux kernel rebuilding, for your 
          reference only.
	  For appropriate details, please refer to the Linux document.
	
 	  For 2.4.x:
	   a. cd /usr/src/linux
	   b. make clean	     /* take a few minutes */
	   c. make dep		     /* take a few minutes */
	   d. make bzImage	     /* take probably 10-20 minutes */
	   e. make modules
	   f. make install	     /* copy boot image to correct position */
	   g. make modules_install		
	   h. Please make sure the boot kernel (vmlinuz) is in the
	      correct position. 
	   i. If you use 'lilo' utility, you should check /etc/lilo.conf 
	      'image' item specified the path which is the 'vmlinuz' path, 
	      or you will load wrong (or old) boot kernel image (vmlinuz).
	      After checking /etc/lilo.conf, please run "lilo".

	  Note that if the result of "make bzImage" is ERROR, then you have to
	  go back to Linux configuration Setup. Type "make menuconfig" in 
          directory /usr/src/linux.

	   For 2.6.x:
	   a. cd /usr/src/linux
	   b. make 	     
	   c. make modules	
	   d. make install
	   e. make modules_install


       3.5.9 Make tty device and special file
          # cd /moxa/mxpcdrv/driver
          # ./mpmknod
          
       3.5.10 Make utility
	  # cd /moxa/mxpcdrv/utility
	  # make clean; make install

       3.5.11 Reboot

   3.6 Custom configuration
       Although this driver already provides you default configuration, you
       still can change the device name and major number. The instruction to
       change these parameters are shown as below.

       Change Device name
       ------------------
       If you'd like to use other device names instead of default naming
       convention, all you have to do is to modify the internal code
       within the shell script "mpmknod". First, you have to open "mpmknod"
       by vi. Locate each line contains "ttyN" and "cun" and change them
       to the device name you desired. "mpmknod" creates the device names
       you need next time executed.

       Change Major number
       -------------------
       If major number 34 and 41 had been occupied, you may have to select
       2 free major numbers for this driver. There are 3 steps to change
       major numbers.

       3.6.1 Find free major numbers
	  In /proc/devices, you may find all the major numbers occupied
	  in the system. Please select 2 major numbers that are available.
	  e.g. 40, 45.
       3.6.2 Create special files
	  Run /moxa/mxpcdrv/driver/mpmknod to create special files with
	  specified major numbers.
       3.6.3 Modify driver with new major number
	  Run vi to open /moxa/mxpcdrv/driver/mxpcdrv.c. Locate the line
	  contains "MXSERMAJOR". Change the content as below.
	  #define	  MXSERMAJOR		  40
	  #define	  MXSERCUMAJOR		  45
       3.6.4 Run "make clean; make install" in /moxa/mxpcdrv/driver.

   3.7 Verify driver installation
       You may refer to /var/log/messages to check the latest status
       log reported by this driver whenever it's activated.
       
-----------------------------------------------------------------------------
4. Utilities
   There are 3 utilities contained in this driver. They are mpdiag, mpmon and
   mpterm. These 3 utilities are released in form of source code. They should
   be compiled into executable file and copied into /usr/bin.

   Before using these utilities, please load driver (refer 3.4 & 3.5 & 3.6) and
   make sure you had run the "mpmknod" utility.

   mpdiag - Diagnostic
   --------------------
   This utility provides the function to display what Moxa PC104 Communication 
   Module found by driver in the system.

   mpmon - Port Monitoring
   -----------------------
   This utility gives the user a quick view about all the MOXA ports'
   activities. One can easily learn each port's total received/transmitted
   (Rx/Tx) character count since the time when the monitoring is started.
   Rx/Tx throughputs per second are also reported in interval basis (e.g.
   the last 5 seconds) and in average basis (since the time the monitoring
   is started). You can reset all ports' count by <HOME> key. <+> <->
   (plus/minus) keys to change the displaying time interval. Press <ENTER>
   on the port, that cursor stay, to view the port's communication
   parameters, signal status, and input/output queue.

   mpterm - Terminal Emulation
   ---------------------------
   This utility provides data sending and receiving ability of all tty ports,
   especially for MOXA ports. It is quite useful for testing simple
   application, for example, sending AT command to a modem connected to the
   port or used as a terminal for login purpose. Note that this is only a
   dumb terminal emulation without handling full screen operation.
-----------------------------------------------------------------------------
5. Setserial

   Supported Setserial parameters are listed as below.

   uart 	  set UART type(16450-->disable FIFO, 16550A-->enable FIFO)
   close_delay	  set the amount of time(in 1/100 of a second) that DTR
		  should be kept low while being closed.
   closing_wait   set the amount of time(in 1/100 of a second) that the
		  serial port should wait for data to be drained while
		  being closed, before the receiver is disable.
   spd_hi	  Use  57.6kb  when  the application requests 38.4kb.
   spd_vhi	  Use  115.2kb	when  the application requests 38.4kb.
   spd_normal	  Use  38.4kb  when  the application requests 38.4kb.

-----------------------------------------------------------------------------
6. Troubleshooting

   The boot time error messages and solutions are stated as clearly as
   possible. If all the possible solutions fail, please contact our technical
   support team to get more help.


   Error msg: More than 4 Moxa PC104 Communication Modules found. Fifth board 
              and after are ignored.
   Solution:
   To avoid this problem, please unplug fifth and after board, because Moxa
   driver supports up to 4 boards.

   Error msg: Request_irq fail, IRQ(?) may be conflict with another device.
   Solution:
   Other PCI or ISA devices occupy the assigned IRQ. If you are not sure
   which device causes the situation, please check /proc/interrupts to find
   free IRQ and simply change another free IRQ for Moxa board.

   Error msg: Board #: C1xx Series(CAP=xxx) interrupt number invalid.
   Solution:
   Each port within the same multiport board shares the same IRQ. Please set
   one IRQ (IRQ doesn't equal to zero) for one Moxa board.

   Error msg: No interrupt vector be set for Moxa ISA board(CAP=xxx).
   Solution:
   Moxa ISA board needs an interrupt vector.Please refer to user's manual
   "Hardware Installation" chapter to set interrupt vector.

   Error msg: Couldn't install MOXA PC104 Communication Module driver!
   Solution:
   Load Moxa driver fail, the major number may conflict with other devices.
   Please refer to previous section 3.7 to change a free major number for
   Moxa driver.

   Error msg: Couldn't install MOXA PC104 Communication Module callout driver!
   Solution:
   Load Moxa callout driver fail, the callout device major number may
   conflict with other devices. Please refer to previous section 3.7 to
   change a free callout device major number for Moxa driver.
   
   
-----------------------------------------------------------------------------