Skip to content

Commit fc73be8

Browse files
committed
updated READMEs
1 parent cfdc18a commit fc73be8

File tree

7 files changed

+24
-8
lines changed

7 files changed

+24
-8
lines changed

00-environment/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
*Concepts you may want to Google beforehand: linux, mac, terminal, compiler, emulator, nasm, qemu*
2+
3+
**Goal: Install the software required to run this tutorial**
4+
15
I'm working on a Mac, though Linux is better because it will have all the standard tools already
26
available for you.
37

01-bootsector-barebones/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
*Concepts you may want to Google beforehand: assembler, BIOS*
22

3+
**Goal: Create a file which the BIOS interprets as a bootable disk**
4+
35
This is very exciting, we're going to create our own boot sector!
46

57
Theory

02-bootsector-print/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
*Concepts you may want to Google beforehand: interrupts, CPU
22
registers*
33

4+
**Goal: Make our previously silent boot sector print some text**
5+
46
We will improve a bit on our infinite-loop boot sector and print
57
something on the screen. We will raise an interrupt for this.
68

03-bootsector-memory/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
*Concepts you may want to Google beforehand: memory offsets, pointers*
22

3+
**Goal: Learn how the computer memory is organized**
4+
35
Please open page 14 [of this document](
46
http://www.cs.bham.ac.uk/~exr/lectures/opsys/10_11/lectures/os-dev.pdf)<sup>1</sup>
57
and look at the figure with the memory layout.

04-bootsector-stack/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
*Concepts you may want to Google beforehand: stack*
22

3+
**Goal: Learn how to use the stack**
4+
35
The usage of the stack is important, so we'll write yet another boot sector
46
with an example.
57

05-bootsector-functions-strings/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
*Concepts you may want to Google beforehand: control structures,
22
function calling, strings*
33

4+
**Goal: Learn how to code basic stuff (loops, functions) with the assembler**
5+
46
We are close to our definitive boot sector.
57

68
In lesson 6 we will start reading from the disk, which is the last step before

README.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -38,19 +38,21 @@ How to use this tutorial
3838
you jump right to folder 05 and don't know why there is a `mov ah, 0x0e`, it's because you missed lecture 02.
3939
Really, just go in order. You can always skip stuff you already know.
4040

41-
2. Read each README first. Especially the first line, which details the concepts you should be familiar with
42-
before reading the code.
41+
2. Open the README and read the first line, which details the concepts you should be familiar with
42+
before reading the code. Google concepts you are not familiar with. The second line states the goals for each lesson.
43+
Read them, because they explain why we do what we do. The "why" is as important as the "how".
44+
45+
3. Read the rest of the README. It is **very concise**.
4346

44-
3. Read the README. It is **very concise**. The only theory is the required to understand the code and there
45-
are tips on what to look at when you open the code file(s)
47+
4. (Optional) Try to write the code files by yourself after reading the README.
4648

47-
4. Look at the code examples. Some times you may be able to write them yourself just from the hints on the README.
49+
5. Look at the code examples. They are extremely well commented.
4850

49-
5. Experiment with them and try to break things. Try to change pointers and registers and see what happens. You know, the usual.
51+
6. (Optional) Experiment with them and try to break things. The only way to make sure you understood something is
52+
trying to break it or replicate it with different commands.
5053

5154

52-
TL;DR: First read the README on each folder, then decide if you will
53-
implement it yourself or just read the provided code files.
55+
TL;DR: First read the README on each folder, then the code files. If you're brave, try to code them yourself.
5456

5557

5658
Contributing

0 commit comments

Comments
 (0)