|
|
1.1 root 1: .TH CYC 3
2: .SH NAME
3: cyc \- Cyclone fiber interface
4: .SH SYNOPSIS
5: .B bind #C /dev
6: .PP
7: .B /dev/cyc
8: .SH DESCRIPTION
9: The
10: .I cyc
11: device drives the Cyclone CVME961
12: .RI ( not
13: 960)
14: card with an attached
15: SQFBR Squall module
16: to provide a high-speed point-to-point 9P link between a CPU
17: server and a file server.
18: Both machines must of course have VME buses.
19: For debugging,
20: the Cyclone may be loaded with on-board
21: software using
22: .B xms
23: (see
24: .IR con (1))
25: and the NINDY ROM supplied with the device.
26: In production, though, it is easiest to
27: replace the ROM with the program in the directory
28: .BR /sys/src/fs/cyc .
29: In either case, the on-board software expects an identical
30: Cyclone to be at the other end of the fiber.
31: One of the boards must be in a CPU server, the other in a
32: file server; the systems configure their respective
33: boards dynamically as appropriate.
34: .PP
35: The driver serves a single file,
36: .BR /dev/cyc .
37: When opened, the file initializes the connection to the file
38: server. The resulting file descriptor should be used only
39: to send and receive 9P messages.
40: Typically
41: .IR boot (8)
42: will open
43: .BR /dev/cyc ,
44: prime the connection by sending
45: .B nop
46: and
47: .B session
48: messages (see
49: .IR attach (5)),
50: and then
51: .B mount
52: (see
53: .IR bind (2))
54: the file descriptor in the CPU server's name space.
55: Thenceforth all activity on
56: .B /dev/cyc
57: will be mediated by the mount driver
58: .IR mnt (3)).
59: .SH FILES
60: .TF /sys/src/fs/cyc
61: .TP
62: .B /sys/src/fs/cyc
63: Directory of on-board software for the Cyclone.
64: .SH SEE ALSO
65: .I
66: CVME960, CVM961 Single Board Computer User's Manual
67: and
68: .I
69: SQFBR User's Manual,
70: Cyclone Microsystems, Inc., New Haven, CT, 1-203-7865536
71: .SH SOURCE
72: .B /sys/src/9/power/devcyc.c
73: .SH BUGS
74: The driver is specific to the SGI Power Series, although the device
75: should operate on any VME bus.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.