From b278b9ec7631deb3953806e15f3a49c1a1fc5a18 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Wed, 25 Apr 2018 20:00:06 +0200 Subject: [PATCH] =?UTF-8?q?Update=20=E2=80=9CWhat's=20next=3F=E2=80=9D=20s?= =?UTF-8?q?ection=20of=20vga=20buffer=20post?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- blog/content/second-edition/posts/03-vga-text-buffer/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/second-edition/posts/03-vga-text-buffer/index.md b/blog/content/second-edition/posts/03-vga-text-buffer/index.md index 51528825..be784939 100644 --- a/blog/content/second-edition/posts/03-vga-text-buffer/index.md +++ b/blog/content/second-edition/posts/03-vga-text-buffer/index.md @@ -616,4 +616,4 @@ In this post we learned about the structure of the VGA text buffer and how it ca We also saw how easy it is to add dependencies on third-party libraries, thanks to cargo. The two dependencies that we added, `lazy_static` and `spin`, are very useful in OS development and we will use them in more places in future posts. ## What's next? -In the next post, we will explore _CPU exceptions_. These exceptions are thrown by the CPU when something illegal happens, such as a division by zero or an access to an unmapped memory page (a so-called “page fault”). Being able to catch and examine these exceptions is very important for debugging future errors. Exception handling is also very similar to the handling of hardware interrupts, which is required for keyboard support. +The next post explains how to set up Rust's built in unit test framework. We will then create some basic unit tests for the VGA buffer module from this post.