Please see the README file for general information.

BEFORE INSTALLING

Remove any old HSF modem drivers, either manually or by
running "rpm -e hsflinmodem" or "make uninstall" if using the
RPM or tar versions of this package respectively.


INSTALLATION INSTRUCTIONS

If your Linux distribution supports RPM (RedHat Package Manager),
and has a recent libc, it is easiest to install the binary RPM package
with METHOD A. If your system has RPM but the distributed binaries are not
suitable, you may use METHOD B. METHOD C is for distributions without
RPM support, or those who prefer not to use RPM.


METHOD A: BINARY RPM PACKAGE (*.{arch}.rpm)

If you have obtained the driver package in RPM format:

1. install the rpm with "rpm -i hsflinmodem-{version}.{arch}.rpm"

2. optionally re-run "hsfconfig" to complete the installation (if necessary)
or to change your modem's configuration.


METHOD B: SOURCE RPM PACKAGE (*.src.rpm)

If no pre-generated binary RPM package is adequate for your system,
you may download the source RPM package and:

1. generate a new binary RPM package for your platform with
"rpm --rebuild hsflinmodem-{version}.src.rpm"

2. install the new binary RPM package as described in METHOD A.


METHOD C: TAR PACKAGE (*.tar.gz)

If you have obtained the driver package in tar format:

1. extract the package with "tar -xzf hsflinmodem-{version}.tar.gz"

2. change to the package directory with "cd hsflinmodem-{version}"

3. run "make install" from the top of the package directory.
(Debian users might need to change the KERNELSRC definition in
modules/common.mak first)

4. run "hsfconfig" to complete the installation and configure your modem.

(Alternatively to this whole procedure you may generate RPMS from the tar
package using rpm -ta hsflinmodem-{version}.tar.gz")


AFTER INSTALLATION

If an error occurred during installation, please see the sections 'BUGS'
and 'REPORTING PROBLEMS' below.

Once the modem is installed and configured, you may access it
as /dev/ttySHSF0 or /dev/cuaHSF0 (call-out device). Additionally,
you can use it via the symbolic link /dev/modem (equivalent to ttySHSF0).

Please review the permissions on the device nodes with "ls -l" to ensure
that they are adequate for your system.

The "hsfconfig" command can be used to change certain modem configuration
options or recompile (generic packages only) the kernel modules after
installation.  Run "hsfconfig --help" for usage information.


CHANGING THE COUNTRY PARAMETER

With "hsfconfig --country" you may select another country supported by
your modem.


MANUALLY UNLOADING THE DRIVERS

The modem drivers can be manually unloaded using the "hsfstop" command.


USING ALTERNATIVE PCI VENDOR AND DEVICE IDS

If your modem uses a chipset supported by the drivers but isn't
recognized by the supplied .inf files, you may use (at your own risk)
"hsfconfig --hwtype" to explicitly configure the PCI vendor and device IDs
of your modem.


DOCUMENTATION

See the included document 100498D_RM_HxF_Released.pdf (viewable with
Adobe Acrobat reader or other PDF readers).


REMOVING THE DRIVER

If for any reason you wish to un-install the HSF drivers from your
system, the proper way to proceed depends on how they were initially
installed.

If you used an RPM installation method, execute "rpm -e hsflinmodem"
to remove the package. If you used the tar method, change your current
directory to where you extracted the archive, and execute "make uninstall"


MORE INFORMATION AND HELP

If you require assistance or need more information, go to:
              http://www.linuxant.com/drivers

Conexant Systems neither distributes nor maintains this package.
PLEASE DO NOT CONTACT CONEXANT REGARDING THIS SOFTWARE!!!


BUGS

A list of currently known problems is included in the file "BUGS".


BAD CONNECTIONS

If you experience sudden disconnects or bad connections, please check
the last call status information, which can be obtained with the
AT#UG command or "cat /proc/driver/hsf/0/lastcallstatus" (2.4 or later).
Alternatively the driver can be configured to automatically log
this data upon carrier loss by adding the "loglastcallstatus=1" parameter
to the "options hsfserial" line in /etc/modules.conf.


REPORTING PROBLEMS

Additional problem reports or patches may be sent to:
	hsflinux-bugs@linuxant.com

Enclosing the output of "hsfconfig --dumpdiag" and the last call status
information if pertinent (see above) in your report can greatly
facilitate problem resolution.

