chenyf
b6d0cc6235
|
||
|---|---|---|
| .. | ||
| README | ||
| am33_2.0-libremote.exp | ||
| androideabi.exp | ||
| arm-ice.exp | ||
| arm-sid.exp | ||
| arm-sim.exp | ||
| basic-sid.exp | ||
| basic-sim.exp | ||
| cris-sim.exp | ||
| d30v-sim.exp | ||
| fr30-sim.exp | ||
| frv-sim.exp | ||
| gdbserver-sample.exp | ||
| i386-sid.exp | ||
| iq2000-sim.exp | ||
| jmr3904-sim.exp | ||
| linux-gdbserver.exp | ||
| linux-libremote.exp | ||
| m68k-sid.exp | ||
| mcore-moto-sim.exp | ||
| mcore-sim.exp | ||
| mips-lnews-sim.exp | ||
| mips-lsi-sim.exp | ||
| mips-sim-idt32.exp | ||
| mips-sim-idt64.exp | ||
| mips-sim-mti32.exp | ||
| mips-sim-mti64.exp | ||
| mips-sim-mti64_64.exp | ||
| mips-sim-mti64_n32.exp | ||
| mips-sim-sde32.exp | ||
| mips-sim-sde64.exp | ||
| mips-sim.exp | ||
| mmixware-sim.exp | ||
| mn10200-sim.exp | ||
| mn10300-sim.exp | ||
| msp430-sim.exp | ||
| mt-sid.exp | ||
| multi-sim.exp | ||
| powerpc-sim.exp | ||
| powerpcle-sim.exp | ||
| rx-sim.exp | ||
| sh-sid.exp | ||
| sh-sim.exp | ||
| sparc-sim.exp | ||
| sparc64-sim.exp | ||
| sparclite-sim-le.exp | ||
| sparclite-sim.exp | ||
| tx39-sim.exp | ||
| unix.exp | ||
| v850-sim.exp | ||
| visium-sim.exp | ||
| vr4100-sim.exp | ||
| vr4111-sim.exp | ||
| vr4300-sim.exp | ||
| xtensa-sim.exp | ||
README
The files in this directory are used to describe the basic configuration of a board. (Note that we use "board" in its loosest sense, referring to either a target or host). The structure of these files is very similar, and I would suggest that you follow this when writing a new one. Two files need to be created for a given board; the appropriate file in this directory, and one in config/. The one in here is used to set up entries in the data array describing the board, while the one in devo/dejagnu/config is used to describe the actions used to actually communicate with the board. A third file (the site-specific machine file) can be used to describe any site-specific functionality, such as port numbers, serial devices, etc.