\fBreicast\fR currently needs BIOS/Flash ROMs of the original Dreamcast. For copyright reasons it is not possible to distribute them bundled with \fBreicast\fR, so you have to dump them from your own Dreamcast. \fBreicast\fR will look for these files in:
.IP
~/.reicast/data/dc_boot.bin
.br
~/.reicast/data/dc_flash.bin
.LP
If you do not supply these files, \fBreicast\fR will fall back to reios, an experimental replacement for the original Dreamcast BIOS. However, your experience might not be as stable and some feature might be missing (e.g. booting to the Dreamcast menu will NOT work).
You can create your own mappings with the \fBreicast-joyconfig\fR tool. You should either put them into the "mappings" folder inside the reicast config directory. As an alternative, you can specify an absolute path (which has to begin with a leading slash "/"):
.IP
[input]
.br
evdev_device_id_1 = X
.br
evdev_mapping_1 = /path/to/my_mapping.cfg
.LP
If you don't specify a mapping file, \fBreicast\fR will use one of the pre-defined mapping files (e.g. for Xbox 360 controllers).
If the evdev input works for you, it's probably best to deactivate the legacy joystick API input:
If your version of \fBreicast\fR is compiled against X11, you might want to disable the built-in X11 keyboard support:
.IP
[input]
.br
enable_x11_keyboard = -1
.LP
.SH"GENERAL OPTIONS"
.TP
\fB-config section:option=value\fR
Temporarily override a value of the config file.
.TP
\fB[IMAGE FILE]\fR
Load a specific image file. If no image is given on the command line, reicast will use the value of the "image" option in the "config" section of the config file.
.SH"AUTHOR"
.TP
\fBreicast\fR is developed by a number of people. A list of contributors can be obtained at: