Should we do board/machine files?

[cascardo/kernel/old_slides/.git] / plano

diff --git a/plano b/plano
index b514521..b8b9892 100644 (file)
--- a/plano
+++ b/plano
@@ -1,9 +1,9 @@
 intro
        linux
-               version history/evolution DO?
-               modules
+               version history/evolution/compatibility DO A LITTLE
                constant change, book is already outdated
                current versioning/development model
+               modules
                build dependencies
                running new/bleeding-edge kernels
 
@@ -13,6 +13,8 @@ concepts
                memory protection/segmentation/pagination
                library calls
                allowed uses (floating point forbidden)
+               concurrency
+               small stack
        libc/system calls
        operating system functions
                process management
@@ -44,6 +46,7 @@ basics
        config/build time options/parameters
        sysfs interface for modules DO?
        printk
+       module loading/unloading/handling
 
 VFS
        center/hub/interface
@@ -64,6 +67,8 @@ device driver subsystem
                netlink DO?
 
 char device
+       MAJOR/MINOR/MKDEV
+
 procfs
 sysfs
 block device DO? STUDY
@@ -144,3 +149,5 @@ kobject DO? advanced
 
 STUDY:
        module owner, concurrency, reference counting
+
+board/machine/architecture files DO?