|
发表于 2002-7-3 13:29:09
|
显示全部楼层
readme
ReadMe file for the
Intel?MD563X-HaM V.92 chipset Linux driver
contents:
1. License
2. Release Notes
3. Installation
4. File Descriptions
5. International Users
6. Beta Tester appreciation
7. Security issues
8. Compilation issues
a. Instructions for Debian Users
b. Kernel Source
9. Comments, ideas, problems, fixes
---------------------------------------------------------------------------------
1. LICENSE
IMPORTANT - read the file "LICENSE.txt" for the INTEL SOFTWARE LICENSE AGREEMENT
BEFORE COPYING, INSTALLING OR USING.
also note:
The serial driver open source code located in the directory "serialdrv"
is work covered under the GNU GENERAL PUBLIC LICENSE (GPL).
The "serialdrv" directory has the GPL in the file "GPL.txt".
---------------------------------------------------------------------------------
2. Release Notes
17 August 2001:
!!!!!!!!!!! you must completely uninstall previous linux HaM driver files.
!!!!!!!!!!! especially /etc/hamregistry.bin and /etc/linhamreg.bin
This PRE release supports 2.4.x kernels.
THIS IS A PRE RELEASE WITH SUPPORT FOR 2.4.X KERNELS!
THERE ARE NO GUARANTEES THAT THIS
DRIVER WILL WORK WITH YOUR LINUX DISTRIBUTION
OR KERNEL VERSION AT THIS TIME.
THE 412-2 CORECODE BINARY WAS COMPILED IN MANDRAKE 8.0.
THE CURRENT LIST OF DISTRIBUTIONS THAT I HAVE
TESTED AND SEEN TO WORK WITH THIS
DRIVER ARE THE FOLLOWING:
* Mandrake 8.0 with Linux HaM version 412-2 and kernel 2.4.3-20mdk
* Redhat 7.1 with Linux HaM version 412-2 and kernel 2.4.2-2
/usr/src/linux symbolic link to kernel source must
be created for the driver to compile
UNVERIFIED WITH 408-2 AT THIS TIME, BUT LIKELY COMPATIBLE:
* SuSE 7.1 with both 2.2 and 2.4 kernels.
* SuSE 7.0
* Redhat 7.0
* reports of 408 ham working on Debian with 2.4 kernel
VERIFIED AS INCOMPATIBLE AT THIS TIME:
* Caldera eDesktop 2.4 (with kernel 2.2.14)
many compile warnings from kernel headers.
no at OK response from modem,
no "/etc/caldera-release" need for distrabution indentification
YOU MAY STILL FIND PROBLEMS ON THESE TESTED VERSIONS.
IF YOU DO, EMAIL ME (see end of this readme, section 9),
SO THAT I MAY FIX IT.
THIS LIST WILL GROW AS MY TESTING CONTINUES AND WITH
FEEDBACK FROM LINMODEM USERS, TESTERS, AND VENDORS.
---------------------------------------------------------------------------------
3. INSTALLATION
Prerequisites:
1. root access
2. bash shell to run install scripts
3. a HaM modem
4. kernel source for the kernel you are running
/usr/src/linux must symbolically point to this source
for the makefiles to work.
6 steps to install
1. login as ROOT
2. extract the archive into a directory with "tar -xvf <archivename>.tgz"
3. cd into the the directory it created.
4. Type: make clean
5. Type: make all
6. Type: make install
The installation script has been designed for the following distributions release versions
mandrake-release
SuSE-release
redhat-release
debian_version (including Corel)
slackware-version
conectiva-version
bluepoint-release
Unknown distributions install modules and utilities but
will not install boot scripts!.
Please examine the haminst script if you have a different distribution.
The driver is split in two. A ham serial driver and core driver.
The core driver must be loaded first since the serial driver depends on it.
The serial driver registers itself as character device major number 240, minor number 1.
The serial driver takes one argument right now, which is a number to override the default major number if you need to.
ATTENTION: if the driver compiles but the script just wont work for you.
Here are the bare minimum steps to get your modem to work.
0. log in as root.
1. insmod -f hamcore.o
2. insmod -f ham.o
2a. you can start "hamregistry" at this point if you wish.
3. rm /dev/ham
4. mknod /dev/ham c 240 1 (note "240" is the default, if it does not work see what /proc/devices says ham's major number is)
5. ln -s /dev/ham /dev/modem
6. start a comm application like minicom and use the modem.
7. see section 3 (International Users) for info on setting the correct country settings.
---------------------------------------------------------------------------------
4. FILE DESCRIPTIONS
haminst installation script to install HaM modules and supporting files
files copied to /lib/modules/(kernel-version)/misc
hamcore.o driver core code module
ham.o pseudo serial driver for HaM, depends on hamcore.o
files copied to /etc/rc.d/... (path differes per distribution)
hamboot boot scrip to start and stop HaM modules
files copied to /usr/sbin
hamregistry hamregistry is the "registry" like tool that the modem uses to get and store persistant data
such as county info and profile strings.
files copied to /etc
linhamreg.bin file that stores the initial persistant data for modem.
---------------------------------------------------------------------------------
5. INTERNATIONAL USERS
hamregistry will store the last country setting you
set in the modem.
in minicom (or equivalent comm application)
the commmand to change country setting is "AT+GCI="
the command takes a t.35 country code in hexadecimal.
below is a list of currently supported t.35 country codes.
you can also put this "AT" command in the init string of
the comm application you are using.
if you are a CTR-21 country I think you should be able to
choose a CTR-21 country on the list and be ok. but
that's no guarantee.
The same goes for countries that are "USA" compatable.
country code , t.35 code
---------------------------
USA 1 B5
ARG 54 07
AUS 61 09
AUT 43 0A
BEL 32 0F
BOL 591 14
BRA 55 16
CHE 41 A6
CHL 56 25
CHN 86 26
COL 57 27
CYP 357 2D
DEU 49 42
DNK 45 31
DOR 47 82
ECU 593 35
ESP 34 A0
FIN 358 3C
FRA 33 3D
GBR 44 B4
GRC 30 46
HKG 852 50
IDN 62 54
IND 91 53
IRL 753 57
ISL 354 52
ISR 972 58
ITA 39 59
JPN 81 00
KOR 82 61
LIE 423 68
LUX 352 69
MEX 52 73
MYS 60 C3
NLD 31 7B
NOR 47 82
NZL 64 7E
PAK 92 84
PAN 507 85
PER 51 88
PHL 63 89
PRT 351 8B
RUS 7 B8
SAU 966 98
SGP 65 9C
SWE 46 A5
THA 66 A9
TUR 90 AE
TWN 886 26
VNM 84 BC
---------------------------------------------------------------------------------
6. Thanks to the following beta testers for their valuable input and suggestions
during the HaM 333 beta test between January 2 - 26, 2001
Sean Walbran
Rob Clark
Marvin Stodolsky
Dominique Duval
Roman Krais
Ulrich Guenther
Marcelino Viana Pinheiro
Thomas S. Iversen
Jospeh Teichman
Michel Bartolone (MED)
Ramon Gonzalez Montoiro
Ryoji Kawagishi
Torsten Vogel
"jandro"
Ian Carr-de Avelon
Helga Weindl
Ed Casas
Bernhard Hoelcker
Alexander "Sasha" Voytov
Albert Woo
Peter Hirschmann
and all of the helpful Linux HaM users
around the world and at www.linmodems.org
---------------------------------------------------------------------------------
7. Security issues
the haminst and hamboot file install the files and device nodes as
root for the owner and group.
this will cause problems for those who want to user the modem to dialout
using an account other than root.
In SuSE, "dialout" is the group used to install the files and device node.
This way, anyone belonging to the "dialout" group can use the modem to dialout.
(take a look at /etc/group)
I did not want the script to allow full access of the modem to everyone without
"root" knowing.
Edit the hamboot and haminst scripts to fit your needs.
---------------------------------------------------------------------------------
8. Compile issues
a. DEBIAN USERS!
the file /usr/include/linux/modversions.h does not exist in debian 2.2
you must comment out the #include<linux/modversion.h> line from both
hamdefs.h files in the HaM source code for it to compile.
b. You will need the kernel source that you are compiling the module for.
some distributions do not automatically install all the neccisary
kernel headers in a default installation. The makefiles look for
the directory "/usr/src/linux/include/linux". "/usr/src/linux" is
a symoblic link to the kernel source you wish to use. Most distributions
should have an available archived kernel source for the kernel version
they are using. Please read the documentation provided with the kernel
source as it is a very importaint part of what "linux" is all about.
If you feel comfortable with compiling the driver with the system header
files in "/usr/include", modifiy the makefile's include paths to point
to "/usr/include" instead of "/usr/src/linux/include"
please refer to article:
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:3785:200105:pdfckkcmemhofipa
for more information concering the "kernel source" issue.
---------------------------------------------------------------------------------
9. Comments, ideas, problems, fixes:
please contact
Dorian S. Araneda
Product Engineer,
Intel Residential Access Division (RAD)
http://developer.intel.com/design/modems/
www.intel.com www.intc.com (ticker: INTC)
110 Horizon Dr., Suite 300, Raleigh, NC 27615
other resources and information on linux controllerless modems can be found on
www.linmodems.org
|
|