FPA_DOWNLOAD(8) System Manager's Manual FPA_DOWNLOAD(8)
fpa_download - download to the Floating Point Accelerator
fpa_download [ -d ] [ -r ] [ -v ]
[ -u ufile ] [ -m mfile ] [ -c cfile ]
fpa_download applies to Sun-3 and Sun-3x systems equipped with either
an FPA or FPA+.
fpa_download writes microcode, map, and constants files to FPA and FPA+
boards. FPA requires a map file; FPA+ does not.
Root execution level is required to download (d,u,m and c options).
fpa_download is called from /etc/rc.local when /dev/fpa exists.
Given no arguments, fpa_download prints whether an FPA, or FPA+ is
-d Download microcode, constants, and map files. Enable default
-r Print microcode and constant revision.
-v Verbose mode.
-u ufile Download microcode from ufile.
-m mfile Download map from mfile (FPA only).
-c cfile Download constants from cfile.
/dev/fpa device file for both FPA and FPA+.
default microcode file (ufile) for FPA.
default constants file (cfile) for FPA
default map file (mfile) for FPA
default microcode file (ufile) for FPA+
default constants file (cfile) for FPA+
The following diagnostics are printed when fpa_download encounters a
serious error and asks the kernel to disable the FPA. This might occur
if the microcode, map, or constants files are corrupted, or if there is
an FPA or system hardware problem.
FPA Download Failed - FPA ioctl failed
An ioctl() on /dev/fpa failed, possibly due to a hung FPA pipe.
FPA Failed Download - FPA Bus Error
Received a SIGFPE.
FPA Failed Download - Upload mismatch
After each file is written to the FPA/FPA+, fpa_download uploads
the contents of FPA memory and compares it with the source.
They should always match.
31 January 1990 FPA_DOWNLOAD(8)