diff options
author | Andreas Baumann <mail@andreasbaumann.cc> | 2017-07-05 14:19:14 +0200 |
---|---|---|
committer | Andreas Baumann <mail@andreasbaumann.cc> | 2017-07-05 14:19:14 +0200 |
commit | d01f574b08357dc0a64adcb14b87c2c1a393c29a (patch) | |
tree | 30f25231cdec0da7b7a1bc23938a63478d3d6ade /BUGS | |
parent | 199aacd93ffca11370dad1c412ab2ef24be85b72 (diff) | |
download | abaos-d01f574b08357dc0a64adcb14b87c2c1a393c29a.tar.gz abaos-d01f574b08357dc0a64adcb14b87c2c1a393c29a.tar.bz2 |
updated bug list
Diffstat (limited to 'BUGS')
-rw-r--r-- | BUGS | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -16,3 +16,12 @@ - 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 + |