Apple-2-HW/aiie
1
0
Fork 0
mirror of https://github.com/JorjBauer/aiie.git synced 2024-11-22 15:31:41 +00:00
Code Issues Projects Releases Wiki Activity

another attempt to make the markdown behave sanely

Browse Source
This commit is contained in:
Jorj Bauer 2017-02-19 19:18:42 -05:00
parent b27cfc7b76
commit 8e155646c9
1 changed files with 19 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@ -46,13 +46,17 @@ While this isn't the purpose of the emulator, it is functional, and is
my first test target for most of the work. With MacOS 10.11.6 and
Homebrew, you can build and run it like this:
``` $ make opencv
$ ./aiie-opencv /path/to/disk.dsk```
<pre>
$ make opencv
$ ./aiie-opencv /path/to/disk.dsk
</pre>
As the name implies, this requires that OpenCV is installed and in
/usr/local/lib. I've done that with Homebrew like this
``` $ brew install opencv```
<pre>
$ brew install opencv
</pre>
"Why OpenCV?" you might ask. Well, it's just because I had code from
another project lying around that directly manipulated OpenCV bitmap
@ -69,22 +73,28 @@ together the MMU, virtual keyboard, and virtual display.
Then there are the physical interfaces, which aren't as well
organized. They exist as globals in globals.cpp:
``` FileManager *g_filemanager = NULL;
<pre>
FileManager *g_filemanager = NULL;
PhysicalDisplay *g_display = NULL;
PhysicalKeyboard *g_keyboard = NULL;
PhysicalSpeaker *g_speaker = NULL;
PhysicalPaddles *g_paddles = NULL;```
PhysicalPaddles *g_paddles = NULL;
</pre>
There are the two globals that point to the VM and the virtual CPU:
``` Cpu *g_cpu = NULL;
VM *g_vm = NULL;```
<pre>
Cpu *g_cpu = NULL;
VM *g_vm = NULL;
</pre>
And there are two global configuration values that probably belong in
some sort of Prefs class:
``` int16_t g_volume;
uint8_t g_displayType;```
<pre>
int16_t g_volume;
uint8_t g_displayType;
</pre>
CPU