diff options
author | Andreas Baumann <mail@andreasbaumann.cc> | 2017-07-14 17:33:27 +0200 |
---|---|---|
committer | Andreas Baumann <mail@andreasbaumann.cc> | 2017-07-14 17:33:27 +0200 |
commit | 2ff50537d6b01e695f53d7fcdf93d3b08dda2e36 (patch) | |
tree | c22e04536ae66c70e8eb9f1fdce2a504a1b91324 | |
parent | 54492def2239a4ded3a624aa8d2abfec50b5ffa0 (diff) | |
download | abaos-2ff50537d6b01e695f53d7fcdf93d3b08dda2e36.tar.gz abaos-2ff50537d6b01e695f53d7fcdf93d3b08dda2e36.tar.bz2 |
updated bug list
-rw-r--r-- | BUGS | 8 |
1 files changed, 0 insertions, 8 deletions
@@ -13,14 +13,6 @@ - real hardware like the Asus EEEPC 701 cannot switch A20 correctly, no clue why? - if a task ends, what should we do? currently we crash -- libc is too closely coupled to kernel code; the initializers, - calling the kernel_panic function, etc. We must decouple with - a special module providing the global variables (from the point - of view of libc, like the console or the memory manager). The - kernel_panic function should be a callback hook we provide from - outside of the library. Then in the libc test directory we have - to implement a stub module for instance using some host functions - like standard io of the host C library - memorymanagement should be a library of the libc or even a standalone library, not part of the kernel directory, get rid of kernel_panic there (this requires the kernel_stub.c kernel_panic to exist in |