source-tree-hierarchy.markdown

 # Source Tree Hierarchy
 - arch : Machine-specific root directory. Put there the machine/processor dependant code.
+    - sh : Renesas SuperH processors and SoC specific code
+        - include/arch : Headers for arch-specific definition (types, constants, inline functions...) that can't fit in arch/generic directory
+        - memory : Some EEPROM-related implementation
+        - modules : Implementations of complex SoC modules (USB, USART...)
+    - generic : Headers holding function declarations expected to be implemented by real machine-specific code
 - bootloader : Current FX-9860 FiXos bootloader. The code is still there because it depends of some kernel details.
 - device : Machine device code (like screen, keyboard, etc...).
     - display : Screen device.
@@ -11,13 +16,13 @@
     - usb : USB device code.
 
 - fs : filesystem code.
-    - casio_smemfs : Casio's Filesystem code.
-    - protofs : ?
-- gcc_fix : ? Gcc fixes?
+    - casio_smemfs : Casio's SMEM Filesystem code.
+    - protofs : Experimental RAM Filesystem, currently only able to contain directories and device nodes
+- gcc_fix : Fixes to handle some libgcc functions (GCC may emit function calls in some circumstances, like for divisions or memory coping operations). This system should be replaced by linking with libgcc instead of providing needed functions soon.
 - interface : This directory is used to place all definitions that are aimed to be used from
 the user space. Think of syscalls, structures and code.
 - loader : executable loader code.
     - elfloader : ELF file format code.
 - sys : system code.
-- user : userspace tempoary code.
-- utils : utility code.
+- user : userspace temporary code.
+- utils : utility functions and definitions.
\ No newline at end of file