Recent changes to wiki

Kernel API specification modified by 0xJarno

0xJarno — Fri, 15 Sep 2017 14:09:32 -0000

--- v4
+++ v5
@@ -1,4 +1,4 @@
-Kernel API specification
+Kernel API specification (deprecated)
 ========================

 THIS DOCUMENT IS NOT UP TO DATE

Pulse boot loader architecture modified by 0xJarno

0xJarno — Sat, 12 Nov 2016 21:24:14 -0000

--- v6
+++ v7
@@ -1,30 +1,43 @@
-Boot loader architecture
-=======================
-Pulse is a one-stage boot loader that loads only one piece of data called the "bootimage". This chunk of data is then used to initialize the GDT, IDT etc. since it contains all this information (in v2, the BCL is used for initialization). It also  contains where to copy this information to so it can change in future.
+Bootloader Architecture
+====================
+Pulse is a simple bootloader that loads only one piece of data called the "bootimage". The bootimage contains a boot catalog to load everything to the proper location, an initializer and as much data as neccesary.
+Conceptually a bootimage captures the whole state of the system, with some limitations.

-Architecture as described in 'boot_arch.txt'
-----------------------------------------------
-Bootloader tasks (v1):
- 1) Gather system information
- 2) Enable A20
- 3) Load bootimage
- 4) Use bootimage GDT, IDT etc. to initialize envoirement
- 5) Transfer control to the kernel
+Bootloader Properties
+-------------------------------
+The bootloader comes in two variants: one which is suited as an MBR (potentially part of GPT) and the other as a simple stand-alone, to be used on a single-os system or on a logical partition. It is
+preffered however to have the Pulse bootloader in the MBR, since it will proved the cleanest interface for a multiboot system. The bootloader is hardcoded to expect the bootimage at a certain LBA adress.

-Bootloader tasks (v2):
- 1) Gather system information
- * Only for booting, not OS
- 2) Enable A20
- 3) Load bootimage
- 4) Execute BCL part of the bootimage
- 5) Transfer control to bootimage
- * Assumes new OS design supporting RM, PM and LM
+Bootloader Tasks
+-------------------------
+  1. Gather system information
+  2. Enable A20
+  3. Load bootimage
+  4. Transfer control to initializer

-BCL (bootloader command list): Entry: byte 1 - 2: SOURCE
- byte 3 - 4: LENGTH
- byte 5 - 6: DESTINATION
- byte 7 - 8: TYPE
- type 0xFFFA: Continue execution of BCL
- type 0xFFFB: Stop execution of BCL
- Asm macro notation: entry(source, length, destination)
- stop()
+Boot Image
+------------------
+The bootimage has the following structure:
+```
+| Offset (decimal, bytes) | Size (bytes) | Description                                                    |
+|-------------------------|--------------|----------------------------------------------------------------|
+| 0                       | 4            | Size of the boot catalog.                                      |
+| 4                       | 4*n          | Boot catalog entries.                                          |
+| 4*(n+1)                 | ?            | Data (size implicitly determined by boot catalog's last entry. |
+```
+
+Each entry in the boot catalog has the following structure:
+```
+| Offset (decimal, bytes) | Size (bytes) | Description                  |
+|-------------------------|--------------|------------------------------|
+| 0                       | 4            | LBA Source adress (reserved) |
+| 4                       | 4            | Memory destination adress    |
+| 8                       | 4            | Chuck size                   |
+```
+
+The bootloader simply loads the whole boot catalog in memory, and then starts loading all
+chucks of data to the right location. The LBA Source adress is ignored, and all data chuncks are
+assumed to be in a continous piece of data right after the boot catalog. This is to improve locality on
+magnetic disks, when flash booting is supported this feature will be enabled. The first entry of the
+catalog must always be the initializer. After loading all chucks the initializer is executed and the
+bootloader may be safely overwritten.

Pulse boot loader architecture modified by 0xJarno

0xJarno — Tue, 14 Jun 2016 18:26:53 -0000

--- v5
+++ v6
@@ -1,6 +1,6 @@
 Boot loader architecture
 =======================
-Pulse is a one-stage boot loader that loads only one piece of data called the "bootimage". This chunk of data is then used to initialize the GDT, IDT et cetera since it contains all this information (in v2, the BCL is used for initialization). It also  contains where to copy this information to so it can change in future.
+Pulse is a one-stage boot loader that loads only one piece of data called the "bootimage". This chunk of data is then used to initialize the GDT, IDT etc. since it contains all this information (in v2, the BCL is used for initialization). It also  contains where to copy this information to so it can change in future.

 Architecture as described in 'boot_arch.txt'
 ----------------------------------------------

Exode modified by 0xJarno

0xJarno — Wed, 02 Sep 2015 19:52:21 -0000

--- v2
+++ v3
@@ -6,12 +6,14 @@
 * Functional
 * Object oriented
 * Declarative (constraint, logic)
+
 Type system
 -
 * Strong
 * Static
 * Effect system
 * Hindley–Milner type system
+
 Special features
 -
 * Query collections or the file system from inside the language

Exode modified by 0xJarno

0xJarno — Wed, 02 Sep 2015 19:51:48 -0000

--- v1
+++ v2
@@ -22,6 +22,7 @@
 Examples
 -
 Simplified implementation of PersistentObject:
+
 ~~~~
 class PersistenObject : Object {
     on System.shutdown {
@@ -29,7 +30,9 @@
     }
 }
 ~~~~
+
 Example of inline ASM:
+
 ~~~~
 operator Int + Int {
     mov ax, #1
@@ -37,7 +40,10 @@
     add ax, bx
     return ax
 }
+~~~~
+
 You can mix high-level and low-level code:
+
 ~~~~
 use System.CPU

@@ -57,7 +63,9 @@
  * ...
  */
  ~~~~
+ 
 Queries:
+
 ~~~~
 numbers = [2, 3, 10, -1, 0, 5, -3]
 for x in numbers where x <= 0 {
@@ -65,7 +73,9 @@
 }
 // -1, 0, -3
 ~~~~
+
 Not convinced?
+
 ~~~~
 // No need for for-in: Exode is an array language
 display (Image in User.fotoAlbum[selectedAlbum] where width > 800 px & height > 600 px)

Exode modified by 0xJarno

0xJarno — Wed, 02 Sep 2015 19:50:03 -0000

Exode is our new programming languages in development. During development of Cloudium OS we saw the need for another language than only pure ASM. Because we didn't want to lose the fine-grained acces ASM provided us, we decided not to go with an existing language like C or C++, but to make our own. This also gives us the opportunity to create a languages specifically tailored to Cloudium OS, to incorporate new ideas and have a much more modern language at the core of the OS, which still allows the low level control of plain old ASM.

Paradigm

Imperative
Functional
Object oriented
Declarative (constraint, logic)
Type system
-
Strong
Static
Effect system
Hindley–Milner type system
Special features
-
Query collections or the file system from inside the language
Built-in support for concurrency (even over the network)
Special support for event handlers
Support for units

Examples

Simplified implementation of PersistentObject:
class PersistenObject : Object {
on System.shutdown {
self.serialize.save(id:self.hash)
}
}
Example of inline ASM:
operator Int + Int {
mov ax, #1
mov bx, #2
add ax, bx
return ax
}
You can mix high-level and low-level code:
use System.CPU

fn main() {
ax, bx, cx = 1, 2, 3
for register: value in registers {
println "(register): (value)"
}
}
/
* AX: 0x0001
* BX: 0x0002
* CX: 0x0003
* DX: 0xFD31
* CS: 0x7D23
* FS: 0x81D3
* ...
/
Queries:
numbers = [2, 3, 10, -1, 0, 5, -3]
for x in numbers where x <= 0 {
print x .. ", "
}
// -1, 0, -3
Not convinced?
// No need for for-in: Exode is an array language
display (Image in User.fotoAlbum[selectedAlbum] where width > 800 px & height > 600 px)
// Equivalent SQL: "select image from userPictures where album = (selectedAlbum) and width > 800 and height > 600"

Pulse boot loader architecture modified by 0xJarno

0xJarno — Sat, 24 May 2014 18:08:10 -0000

--- v4
+++ v5
@@ -2,7 +2,7 @@
 =======================
 Pulse is a one-stage boot loader that loads only one piece of data called the "bootimage". This chunk of data is then used to initialize the GDT, IDT et cetera since it contains all this information (in v2, the BCL is used for initialization). It also  contains where to copy this information to so it can change in future.

-Architecture like described in 'boot_arch.txt'
+Architecture as described in 'boot_arch.txt'
 ----------------------------------------------
 Bootloader tasks (v1):
  1) Gather system information

Plan modified by 0xJarno

0xJarno — Sat, 24 May 2014 18:07:49 -0000

--- v1
+++ v2
@@ -1,4 +1,7 @@
 = Plan =
+
+THIS DOCUMENT IS NOT UP TO DATE
+THIS DOCUMENT IS IN CONSIDERATION OF DELETION

 == Bootloader ==
  # Complete current (release last alpha version)

Kernel API specification modified by 0xJarno

0xJarno — Sat, 24 May 2014 18:06:58 -0000

--- v3
+++ v4
@@ -5,7 +5,7 @@

 This document describes the kernel API

-Like in the API_v1.0_spec.txt file
+As in the API_v1.0_spec.txt file
 ----------------------------------
 KERNEL API V1.0 SPECIFICATION
 Written by Jarno Van Schoor

Nucleo kernel architecture modified by 0xJarno

0xJarno — Sat, 24 May 2014 18:06:23 -0000

--- v4
+++ v5
@@ -4,7 +4,7 @@

 This document describes the internal architecture of the Nucleo kernel

-Like in the kernel.txt file
+As in the kernel.txt file
 ---------------------------
  message pasing ("http://wiki.osdev.org/Message_Passing")
        type: reliable on top of unreliable