OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [tags/] [before_ORP/] [uclinux/] [uClinux-2.0.x/] [Documentation/] [networking/] [tlan.README] - Blame information for rev 901

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 199 simons
TLAN driver for Linux, version 1.0
2
README
3
 
4
Well, I'm back.  The TLAN driver seems pretty stable, so I'm
5
declaring this cycle of development finished, and calling the
6
driver 1.0.  I will, of course continue to work on improving
7
the driver, and work towards a 2.0 release.
8
 
9
 
10
 
11
I.  Supported Devices.
12
 
13
    Only PCI devices will work with this driver.
14
 
15
    Supported:
16
    Vendor ID   Device ID       Name
17
    0e11        ae32            Compaq Netelligent 10/100 TX PCI UTP
18
    0e11        ae34            Compaq Netelligent 10 T PCI UTP
19
    0e11        ae35            Compaq Integrated NetFlex 3/P
20
    0e11        ae40            Compaq Netelligent Dual 10/100 TX PCI UTP
21
    0e11        ae43            Compaq Netelligent Integrated 10/100 TX UTP
22
    0e11        b011            Compaq Netelligent 10/100 TX Embedded UTP
23
    0e11        b012            Compaq Netelligent 10 T/2 PCI UTP/Coax
24
    0e11        b030            Compaq Netelligent 10/100 TX UTP
25
    0e11        f130            Compaq NetFlex 3/P
26
    0e11        f150            Compaq NetFlex 3/P
27
    108d        0012            Olicom OC-2325
28
    108d        0013            Olicom OC-2183
29
    108d        0014            Olicom OC-2326
30
 
31
 
32
    Caveats:
33
 
34
    I am not sure if 100BaseTX daughterboards (for those cards which
35
    support such things) will work.  I haven't had any solid evidence
36
    either way.
37
 
38
    However, if a card supports 100BaseTx without requiring an add
39
    on daughterboard, it should work with 100BaseTx.
40
 
41
    The "Netelligent 10 T/2 PCI UTP/Coax" (b012) device is untested,
42
    but I do not expect any problems.
43
 
44
 
45
II.  Building the Driver.
46
 
47
    The TLAN driver may be compiled into the kernel, or it may be compiled
48
    as a module separately, or in the kernel.  A patch is included for
49
    2.0.29 (which also works for 2.0.30, 2.0.31, and 2.0.32).
50
 
51
    To compile it as part of the kernel:
52
        1. Download and untar the TLAN driver package.
53
        2. If your kernel is 2.1.45 or later, you do not need to patch the
54
           kernel sources.  Copy the tlan.c and tlan.h to drivers/net in
55
           the kernel source tree.
56
        3. Otherwise, apply the appropriate patch for your kernel.  For
57
           example:
58
 
59
               cd /usr/src/linux
60
               patch -p1 < kernel.2.0.29
61
 
62
        4. Copy the files tlan.c and tlan.h from the TLAN package to the
63
           directory drivers/net in the Linux kernel source tree.
64
        5. Configure your kernel for the TLAN driver.  Answer 'Y' when
65
           prompted to ask about experimental code (the first question).
66
           Then answer 'Y' when prompted if to include TI ThunderLAN
67
           support.  If you want the driver compiled as a module, answer 'M'
68
           instead of 'Y'.
69
        6. Make the kernel and, if necessary, the modules.
70
 
71
    To compile the TLAN driver independently:
72
        1. Download and untar the TLAN driver package.
73
        2. Change to the tlan directory.
74
        3. If you are NOT using a versioned kernel (ie, want an non-
75
           versioned module), edit the Makefile, and comment out the
76
           line:
77
                 MODVERSIONS = -DMODVERSIONS
78
        4. Run 'make'.
79
 
80
 
81
III.  Driver Options
82
        1. You can append debug=x to the end of the insmod line to get
83
           debug messages, where x is a bit field where the bits mean
84
           the following:
85
 
86
           0x01         Turn on general debugging messages.
87
           0x02         Turn on receive debugging messages.
88
           0x04         Turn on transmit debugging messages.
89
           0x08         Turn on list debugging messsages.
90
 
91
        2. You can append aui=1 to the end of the insmod line to cause
92
           the adapter to use the AUI interface instead of the 10 Base T
93
           interface.  This is also what to do if you want to use the BNC
94
           connector on a TLAN based device.  (Setting this option on a
95
           device that does not have an AUI/BNC connector will probably
96
           cause it to not function correctly.)
97
 
98
        4. You can set duplex=1 to force half duplex, and duplex=2 to
99
           force full duplex.
100
 
101
        5. You can set speed=10 to force 10Mbs operation, and speed=100Mbs
102
           to force 100Mbs operation. (I'm not sure what will happen
103
           if a card which only supports 10Mbs is forced into 100Mbs
104
           mode.)
105
 
106
        3. If the driver is built into the kernel, you can use the 3rd
107
           and 4th parameters to set aui and debug respectively.  For
108
           example:
109
 
110
           ether=0,0,0x1,0x7,eth0
111
 
112
           This sets aui to 0x1 and debug to 0x7, assuming eth0 is a
113
           supported TLAN device.
114
 
115
           The bits in the third byte are assigned as follows:
116
 
117
                0x01 = aui
118
                0x02 = use SA_INTERRUPT flag when reserving the irq.
119
                0x04 = use half duplex
120
                0x08 = use full duplex
121
                0x10 = use 10BaseT
122
                0x20 = use 100BaseTx
123
 
124
 
125
IV.  Things to try if you have problems.
126
        1. Make sure your card's PCI id is among those listed in
127
           section I, above.
128
        1. Make sure routing is correct.
129
        2. If you are using a 2.1.x kernel, try to duplicate the
130
           problem on a 2.0.x (preferably 2.0.29 or 2.0.30) kernel.
131
 
132
 
133
There is also a tlan mailing list which you can join by sending "subscribe tlan"
134
in the body of an email to majordomo@vuser.vu.union.edu.
135
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.