Return to README.OLD CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / new / hyper / hyroute

Annotation of 43BSDTahoe/new/hyper/hyroute/README.OLD, revision 1.1.1.1

1.1       root        1: This is release 2.1 of the hyperchannel driver and related programs.
                      2: As far as I know it should work fine.
                      3: 
                      4: We are actively using on one machine at Tek (soon to bring up a few
                      5: more machines).  I have used it to succesfully communicate with a CDC
                      6: Cyber, vax/unix under unet, and PDP-11's under unix/unet.  It is
                      7: working on a 780.  I have not tested it on a 750 or 730 although I see
                      8: no reason why it should have difficulty.
                      9: 
                     10: This driver has code to support the older DR-11B style interface for
                     11: the Hyperchannel.  This code has not been tested in this version of the
                     12: driver.  All DR-11B interfaces have been replaced with PI-13s at Tek.
                     13: I strongly reccomend that you stay away from DR11-B's.  The PI-13's are
                     14: brain damaged, but less so.
                     15: 
                     16: We have been noticing occasional glitches on the power fail line.  This
                     17: is happening on at least 3 of our adapters, under both 4.1a and Unet so
                     18: I don't think it's software.  These are almost immediately recovered
                     19: from so they don't cause major problems.  The power fail code calls
                     20: if_drop which might interrupt established virtual circuits.  I have
                     21: been thinking of adding a delay in the call to if_drop so that it only
                     22: gets called if the power is down for more than 20 seconds or so.  If
                     23: they can't get our hardware fixed I will probably go ahead and do that.
                     24: 
                     25: This version of the driver does not use the additional address family
                     26: that we had talked about.  Thus this driver cannot be used to do things
                     27: like gather statistice from remote adapters or program link adapters.
                     28: Eventually I plan on fixing that.
                     29: 
                     30: The HYROUTE define turns on the routing code.  If you have a completely
                     31: flat hyperchannel network (e.g. any adapter is directly reachable from
                     32: every other adapter) then you don't need routing turned on (except
                     33: maybe to use access codes or to specify trunks to try).
                     34: 
                     35: The HYLOG code thurns on adapter command logging.  The hylog program is
                     36: used to read the log.  The log beffer is currently 16k bytes.  This
                     37: probably excessive and is easily cut back (see if_hy.h).
                     38: 
                     39: The HYELOG is an independant histogram of the error codes returned from
                     40: the status command (one axis) and a subset of the driver sytates (the
                     41: other axis).  There is currently no program to present the data in a
                     42: meaningful form although it is not too difficult to get with adb.
                     43: HYELOG and HYLOG are completely independant.
                     44: 
                     45:        Steve Glaser
                     46:        Tektronix M/S 92-515
                     47:        P.O. Box 500
                     48:        Beaverton Or, 97077
                     49: 
                     50:        (503) 629-1915 (work)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.