Use input buffer watermarks of TTYHOG-512 (high) and (high)*7/8
(low) instead of TTYHOG/2 (high) and TTYHOG/5 (low) to agree with
some drivers. 512 is magic and some things depended on TTYHOG/2
>= TTYHOG-512 to work; now they depend on the 512 magic not changing
and TTYHOG-512 being significantly larger than 0. This should be
handled in ttsetwater().
Separate the decision about whether to do input flow control from
doing it. ttyblock() now just starts input flow control (hardware
and/or software) and there is a new function ttyunblock() to stop
it. The decisions are the same except for the watermark changes
and allowing for input expansion for PARMRK.
When flushing input, try harder at first to send a start character
if required, but give up if the first attempt fails.
cy.c, rc.c, sio.c:
Simplify: let ttyinput() handle input flow control if it is not
being bypassed. Use ttyblock() to start flow control otherwise.
rc.c:
Use same input flow control test as elsewhere: test in a more
efficient order and start flow control at >= highwater instead of
at > highwater.
$Id: README.le,v 1.1 1994/10/01 20:15:43 wollman Exp $
----------------
This driver is in no way supported by Digital Equipment. See the
disclaimers in the sources for more.
This driver supports all the DEC EtherWORKS III NICs (DE203, DE204,
and DE205) and the later DEC EtherWORKS II NICs (DE200, DE201, DE202,
DE422). DEPCA-style boards prior to the DE200 have not been tested
and may not work.
This driver is not EISA aware. If you are using a DE422 or have
configured the EtherWORKS III in EISA mode, make sure you specify
the I/O port properly as this driver will *not* probe for it.
(The I/O port should be 0xNc00 where N is the EISA slot number).
This driver does not yet use the full 128KB allowed by the DE422.
Someday, it might. For EtherWORKS III NICs, the driver will override
the EEPROM setting of MemoryMode and *always* use the 2K for best
results.
The driver includes full support for both BPF and IP Multicast.
[All paths are relative to the top of sys source area, usually
/usr/src/sys.]
The following files need to be moved into their respective
directories:
if_le.c --> i386/isa
am7990.h --> i386/isa/ic
lemac.h --> i386/isa/ic
You will need to apply the patch provided in pat.files.i386 to
i386/conf/files.i386 file.
After that is done you will need to edit your config file (in
i386/conf) and a line similar to:
device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr
[The above line assumes the board is still at the factory defaults.]
Change the port, irq, and iomem value if needed to your configuration.
Now you are ready to rebuild your kernel, reboot, and see if the
driver can configure your board. When the system boots, you will
hopefully something close to:
EtherWORKS II:
le0 at 0x300-0x30f irq 5 maddr 0xd0000 msize 65536 on isa
le0: DE202 ethernet address 08:00:2b:2d:c8:45
bpf: le0 attached
EtherWORKS III:
le0 at 0x320-0x33f irq 5 maddr 0xd0000 msize 2048 on isa
le0: DE205-AB ethernet address 08:00:2b:bb:23:e0
le0 attached
in the startup log. If so, the board configured properly and
should be ready to use.
--
Mail: thomas@lkg.dec.com
URL: http://ftp.digital.com/~thomas/
f3b37f91c1