RN(4) BSD Programmer's Manual RN(4)NAMErn - SDL Communications RISCom/N1 high-speed synchronous interface
SYNOPSIS
rn0 at isa? port 0x220 iomem 0xe0000 iosiz 65536
DESCRIPTION
The rn interface provides a point-to-point bit-synchronous serial connec-
tion with speeds up to 4 Mb/s using HDLC frame format. It uses a switch-
selectable block of 8 I/O ports in the range 0x200 through 0x3f0. The
block must be aligned on a 16 port boundary. The jumper-selectable in-
terrupt level is detected at autoconfiguration time or alternatively can
be specified in the system configuration file. Supported IRQs are: 2(9),
3, 4, 5, 10, 11, 12 and 15. The RISCom/N1 board requires a 16, 32 or 64
Kb I/O memory window aligned at a 16 KB boundary (the base address and
size should be specified in the system configuration file). The
RISCom/N1 board should be installed in a 16-bit slot.
Supported synchronous serial encapsulation protocols are described in
p2p(4).
DIAGNOSTICS
The following diagnostics may be printed during autoconfiguration:
rn%d: illegal base address %x
Invalid port specification in kernel config file.
rn%d: illegal memory window size %d
Invalid I/O memory window size in kernel config file.
rn%d: non-aligned memory window (at %x)
Invalid I/O memory base address in kernel config file.
rn%d: can't alloc memory
The probe routine cannot allocate temporary memory. Should never happen.
rn%d: illegal IRQ %d
Invalid IRQ specification in kernel config file.
rn%d: init failed
Initialization sequence failed - hardware problem.
rn%d: memory test failed
Error in on-board memory; this is a hardware problem.
rn%d: no response
Network controller not responding; this is a hardware problem.
rn%d: lost intr
Lost interrupt. This is a warning.
rn%d: invalid status %x
Invalid status code received from network controller; most likely cause
is incorrect ISA bus timing.
rn%d: tx queue botched (0x%x)
Buffer list corrupted due to data error in I/O memory; most likely cause
is incorrect ISA bus timing.
rn%d: status table overflow
Network controller indicates status table overflow; the problem may be
caused by dribble on interface control leads.
rn%d: cannot set modes
Loading link parameters in the network controller failed. This is a
hardware problem.
SEE ALSOintro(4), inet(4), p2p(4), ifconfig(8)BSDI BSD/OS March 1, 1993 2