2. Compilation, Installation, and Startup

2.1. Prerequisites

• A 2.2.16 series (or later) Linux kernel source tree

• An appropriate set of module utilities

• gcc version 2.7.x or later

If you are building the ACP Modem driver and application, you need to have a complete Linux source tree for your kernel, not just an up-to-date kernel image.

2.2. Building and Installing Source

1. Use tar xzvf mwavem-yyyymmdd.tar.gz to unpack the distribution.

2. Change directories with cd mwavem-yyyymmdd

3. Use the ./configure command to configure the build options. Issue ./configure --help to view all of the options. The defaults are probably okay though.

4. Use the make command to build all of the ACP Modem binaries.

   	NOTE
   	Your gcc package should be at least at the 2.7.x level. Check your /usr/src/linux/Documentation/Changes file for the minimum version information.

5. Use make install to install the mwavem binary, mwavem.conf configuration, DSPs, and module device driver files and to create the /dev/modems/mwave device node.

2.3. Setting Things Up

In the [WORLDTRADE] section of your mwavem.conf file, set the Country= parameter to your country access code.

	NOTE
	The mwavem.conf file is installed in the /usr/local/etc directory unless you specified otherwise during the build process

Country information (including access codes) are listed in the mwavem.conf file. For example, for France the following section is present:

[Telephony\Country List\33]
CountryCode=00000021
Name=France
SameAreaRule=0FG
LongDistanceRule=0FG
InternationsalRule=00EFG

To set France to be your configured country in the [WORLDTRADE] section of mwavem.conf,

set Country=33

2.4. Runtime

An initialization script has been provided which may be used to to start, stop, or check the status of the ACP Modem driver and application. It has been successfully run on the Debian, Slackware, SuSE, and Red Hat distributions and should run on any of their derivitives. If you are using the runtime script, it will load the mwave device driver module, configure the serial port, and start the mwave manager for you. All of the options which can be passed to the device driver module, along with some options for the script itself, can be configured by uncommenting and editing the appropriate variables at the beginning of the script.

The mwaved startup script can be found in the src/mwavem directory of the source distribution. If you are running the Red Hat distribution, you can copy the script to your /etc/rc.d/init.d directory and issue the ntsysv command in order to enable it at boot time. If not using Red Hat, see the documentation for your distribution for information on how to set this up to run at boot time.

It is recommended that you use the provided mwaved script. If you are not using the script, however, the following sections will describe how to manually start the device driver and application.

2.4.1. Loading the ACP device driver

To load the mwave device driver use

insmod mwave

or

modprobe mwave

The following arguments may be supplied with the insmod command:

	NOTE
	The following arguments are not persistent from boot to boot (i.e. We are not saving them in the BIOS).

• tp3780i_dsp_irq=5/7/10/11/15

  This parameter allows you to configure the IRQ used by the DSP if the DSP IRQ was not set and stored in BIOS by the Thinkpad™ configuration utility.

• tp3780i_dsp_io=0x130/0x350/0x0070/0xDB0

  This parameter allows you to configure the I/O range used by the DSP if the DSP I/O range was not set and stored in the BIOS by the Thinkpad™ configuration utility.

• tp3780i_uart_irq=3/4

  This parameter allows you to configure the IRQ used by the ACP UART if the Mwave's UART IRQ was not set and stored in BIOS by the Thinkpad™ configuration utility.

• tp3780i_uart_io=0x3f8/0x2f8/0x3E8/0x2E8

  This parameter allows you to configure the I/O range used by the ACP UART if the UART I/O range was not set and stored in BIOS by the Thinkpad™ configuration utility.

The following code is an example of how to run DSP using ttyS1 resources:

insmod mwave tp3780i_dsp_irq=10 tp3780i_dsp_io=0x0130 tp3780i_uart_irq=3 tp3780i_uart_io=0x2f8

	NOTE
	The mwave is unable to check for resource conflicts. It is the your responsibility to ensure that none of the resources specified conflict with other devices.

You can use the tpctl package on Linux or the Thinkpad™ configuration utility on Windows NT or DOS to manage the configuration of Thinkpad™ related resources.