summaryrefslogtreecommitdiff
path: root/doc/directions.txt
diff options
context:
space:
mode:
authorAlex AUVOLAT <alexis211@gmail.com>2013-07-10 21:17:50 +0200
committerAlex AUVOLAT <alexis211@gmail.com>2013-07-10 21:17:50 +0200
commit78d7ffce4861dea5624ff29ceb39f1643dff8235 (patch)
tree6b41c052e48398f7520013622f0b1b9b9190259a /doc/directions.txt
parentfadf399405ca5d918dd5e1182fadc3d82f6bc900 (diff)
downloadTCE-78d7ffce4861dea5624ff29ceb39f1643dff8235.tar.gz
TCE-78d7ffce4861dea5624ff29ceb39f1643dff8235.zip
Serial port used for writing kernel output.
Project: give total control to userland over display/input devices.
Diffstat (limited to 'doc/directions.txt')
-rw-r--r--doc/directions.txt24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/directions.txt b/doc/directions.txt
new file mode 100644
index 0000000..31b6431
--- /dev/null
+++ b/doc/directions.txt
@@ -0,0 +1,24 @@
+Ideas for T/CE's future :
+
+1. Give control to userland
+
+- Provide IPC : we must implement FIFO's and sockets
+- Do not provide VT emulation, instead provide direct write access to
+the video memory. Also provide direct write access to the framebuffer
+when that is implemented. Then, code a display server that does all the
+emulating.
+
+2. Review file management syscalls
+
+- Should keeping track of file position be the job of the kernel ?
+Not sure...
+- Possibility of mmap'ing files. Consequence : shared memory.
+
+3. Review process management
+
+- fork/exec is cool. How does windows work ?
+- Dynamic linking ? Environment variables ? Users ?
+
+4. Have a graphical user interface, just for fun. Then add a few simple
+programs, just for fun.o
+