From 309742463d613137b5eb047311eab56b75ce1052 Mon Sep 17 00:00:00 2001 From: Syed Muhammad Hamza Raza <49732070+HamzaRaza786@users.noreply.github.com> Date: Tue, 6 Feb 2024 12:24:06 +0500 Subject: [PATCH] Update vga-text-buffer failed link for normal reads and write. Previously the hyperlink for 'supports normal reads and writes' in post 3 was redirecting to a page not found, as I guess Stanford has remove that link. So I have added the correct link, which redirects to Stanford's Secure Systems Group, where they have the deails about CS140 course and relevant pintos docs. --- blog/content/edition-2/posts/03-vga-text-buffer/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/edition-2/posts/03-vga-text-buffer/index.md b/blog/content/edition-2/posts/03-vga-text-buffer/index.md index 82d432bd1..c7b01725d 100644 --- a/blog/content/edition-2/posts/03-vga-text-buffer/index.md +++ b/blog/content/edition-2/posts/03-vga-text-buffer/index.md @@ -60,7 +60,7 @@ The VGA text buffer is accessible via [memory-mapped I/O] to the address `0xb800 Note that memory-mapped hardware might not support all normal RAM operations. For example, a device could only support byte-wise reads and return junk when a `u64` is read. Fortunately, the text buffer [supports normal reads and writes], so we don't have to treat it in a special way. -[supports normal reads and writes]: https://web.stanford.edu/class/cs140/projects/pintos/specs/freevga/vga/vgamem.htm#manip +[supports normal reads and writes]: https://www.scs.stanford.edu/21wi-cs140/pintos/specs/freevga/vga/vga.htm ## A Rust Module Now that we know how the VGA buffer works, we can create a Rust module to handle printing: