ReadDrvs.txt ============ The Drvs, drivers directory contains the files for the MC68360 driver module. The source code included in Version 0.3 Release corresponds exactly to the binary on the flash EPROMS on the M68360 0UADS Board. The only exceptions are: 1) Sources for the software user interface of 360sw module are not included, so this would require additional code for interfacing with the other modules. 2) Sources for the file transfer module of the 360sw software are not included. In addition to source files included with the release, makefiles have been included for compiling the system on a Microtec C cross compiler for a 68K (running on UNIX). Minor changes to the makefiles may be necessary for any other software environment. The following should be noted about all the makefiles: 1. $HOME/quicc/ is assummed to be where all your directories exist or have been extracted to. 2. You must have access to a CPU32 C cross-compiler. 3. The user-interface module will generate calls to routines for doing 32-bit arithmetic (multply, divide, modulo). These routines are usually supplied with standard cross-development systems and are not provided in the source release (since not explicitly called, their names and calling conventions will differ from one compiler to another). The makefile in lib expects to find these routines in a file called rt.s which you must supply before trying to compile the user-interface module. 4. Each of the makefiles may be passed three variables: OPTIONS (a list of options passed to the C compiler), C (the name of the CPU32 C cross-compiler) and LD (the name of the Cross loader). To compile the system using the distributed makefiles: (the examples below assume the option -O is required, and that your cross-compiler is known as cc00) 1. Create the directories in which the binary files will be kept for lib and each of the modules to be compiled. For example, mkdir lib/.o drvs/.o lapb/.o lapd/.o 2. Make the library routines cd lib/.o make OPTIONS="-O" C="cc00" -f ../makefile 3. Make all of the modules as necessary. For example, cd HOME/quicc/drvs/.o make OPTIONS="-O" C="cc00" -f ../makefile driver cd HOME/quicc/lapb/.o make OPTIONS="-O" C="cc00" -f ../makefile lapb cd HOME/quicc/lapd/.o make OPTIONS="-O" C="cc00" -f ../makefile lapd cd HOME/quicc/x25/.o make OPTIONS="-O" C="cc00" -f ../makefile x25 Note for MS-DOS Source Release: ------------------------------- The source files are available in IBM/PC format (MS-DOS) diskettes. The source files (and makefiles) were created on a UNIX computer and transferred to the IBM/PC. Since MS-DOS imposes restrictions on the length of filenames, please note that the following files will be truncated to 8 characters plus the extension. If the files are compiled on the IBM/PC, the makefiles will need to be modified to reflect the "new" filenames. UNIX Names: Driver files in quicc/drvs: timekeeper.c registers.h LAPD files in quicc/lapd: lapd_l2mng.c lapd_rxui.c lapd_txui.c lapd_getadr.c lapd_init.c lapd_tmexp.c lapd_busy.c LAPB files in quicc/lapb: lapb_frmr.c lapb_getadr.c lapb_init.c lapb_conn.c lapb_tmexp.c lapb_busy.c lapb_frmr.c Bisync files in quicc/bsyn: bsc_ascii.c X.25 file in quicc/x25: online_reg.h x25_getadr.c x25_olreg.c x25_setup.c x25_tmexp.c Two symbol tables of the software module that runs on the M68360 QUADS board (360sw) under the Motorola EDX 1.2 real-time kernel are included. The symbol tables contains a cross reference table as well. The file Q_DrV0_3.sym is the symbol table for s-record file Q_DrV0_3.srx, that can be programmed to the DRAM on the QUADS board. The file Q_FlV0_3.sym is the symbol table for the s-record file Q_FlV0_3.srx, that can be programmed to the FLASH EPROM on the QUADS board.