1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
<table class="head">
<tr>
<td class="head-ltitle">EC(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">EC(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">ec</code> — <span class="Nd">driver for
3Com EtherLink II (3c503) ISA bus Ethernet cards</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">ec0 at isa? port 0x250 iomem 0xd8000 irq
9</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">ec</code> device driver supports 3Com
EtherLink II (3c503) Ethernet cards for ISA bus which are based on the
National Semiconductor DP8390/WD83C690 Ethernet interface chips.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="MEDIA_SELECTION"><a class="permalink" href="#MEDIA_SELECTION">MEDIA
SELECTION</a></h1>
<p class="Pp">The EtherLink II supports two media types on a single card. All
support the AUI media type. The other media is either BNC or UTP behind a
transceiver. Software cannot differentiate between BNC and UTP cards.</p>
<p class="Pp" id="10base5">To enable the AUI media, select the
<a class="permalink" href="#10base5"><i class="Em">10base5</i></a> or
<a class="permalink" href="#aui"><i class="Em" id="aui">aui</i></a> media
type with <a class="Xr">ifconfig(8)</a>'s <code class="Cm">media</code>
directive. To select the other media (BNC or UTP), select the
<a class="permalink" href="#10base2"><i class="Em" id="10base2">10base2</i></a>
or <a class="permalink" href="#bnc"><i class="Em" id="bnc">bnc</i></a> media
type.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>ec0: wildcarded IRQ is not allowed</dt>
<dd>
<p class="Pp">The IRQ was wildcarded in the kernel configuration file. This
is not supported.</p>
</dd>
<dt>ec0: invalid IRQ <n>, must be 3, 4, 5, or 9</dt>
<dd>
<p class="Pp">An IRQ other than the above IRQ values was specified in the
kernel configuration file. The EtherLink II hardware only supports the
above listed IRQ values.</p>
</dd>
<dt>ec0: failed to clear shared memory at offset <off></dt>
<dd>
<p class="Pp" id="iomem">The memory test was unable to clear shared the
interface's shared memory region. This often indicates that the card is
configured at a conflicting
<a class="permalink" href="#iomem"><i class="Em">iomem</i></a>
address.</p>
</dd>
<dt>ec0: warning - receiver ring buffer overrun</dt>
<dd>
<p class="Pp">The DP8390 Ethernet chip used by this board implements a
shared-memory ring-buffer to store incoming packets. The 3c503 usually
has only 8K bytes of shared memory. This is only enough room for about 4
full-size (1500 byte) packets. This can sometimes be a problem,
especially on the original 3c503, because these boards' shared-memory
access speed is quite slow; typically only about 1MB/second. The
overhead of this slow memory access, and the fact that there is only
room for 4 full-sized packets means that the ring-buffer will
occasionally overrun.</p>
<p class="Pp">When an overrun occurs, the board must be reset to avoid a
lockup problem in early revision DP8390 Ethernet chips. Resetting the
board causes all of the data in the ring-buffer to be lost, requiring
the data to be retransmitted/received, congesting the board further.
Because of this, maximum throughput on these boards is only about
400-600K bytes per second.</p>
<p class="Pp">This problem is exacerbated by NFS because the 8-bit boards
lack sufficient packet buffer memory to support the default 8K byte
packets that NFS and other protocols use as their default. If these
cards must be used with NFS, use the <a class="Xr">mount_nfs(8)</a>
<code class="Fl">-r</code> and <code class="Fl">-w</code> options in
<span class="Pa">/etc/fstab</span> to limit NFS's packet size. 4K (4096)
byte packets generally work.</p>
</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
ALSO</a></h1>
<p class="Pp"><a class="Xr">ifmedia(4)</a>, <a class="Xr">intro(4)</a>,
<a class="Xr">isa(4)</a>, <a class="Xr">ifconfig(8)</a>,
<a class="Xr">mount_nfs(8)</a></p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">October 20, 1997</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|
