02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9<br />

Documentation <strong>Guide</strong>lines<br />

Table 9-2<br />

Common Acronyms<br />

Acronym<br />

CPU<br />

EOF<br />

fd<br />

FTP<br />

IP<br />

NFS<br />

PPP<br />

pty<br />

RAM<br />

ROM<br />

RSH<br />

TCP<br />

TFTP<br />

tty<br />

Definition<br />

Central Processing Unit<br />

End-Of-File<br />

file descriptor<br />

File Transfer Protocol<br />

Internel Protocol<br />

Network File System<br />

Point-to-Point Protocol<br />

pseudo terminal device<br />

Random Access Memory<br />

Read-Only Memory<br />

Remote Shell<br />

Transmission Control Protocol<br />

Trivial File Transfer Protocol<br />

terminal device<br />

9<br />

Board Names<br />

Names used for target VME boards should correspond to the names used by their<br />

suppliers; for example, MV135 is not an acceptable name for the MVME135.<br />

When multiple board models are covered by the same board support package, and<br />

the portion of their names that differs is separated by a slash ( / ) or a hyphen ( - ),<br />

these portions can be repeated, each separated by a comma and a space. See the<br />

examples below:<br />

Force SYS68K/CPU-21, -29, -32<br />

Heurikon HK68/V2F, V20, V2FA<br />

However:<br />

Motorola MVME147, MVME147S-1<br />

179

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!