From 9437656d5cab1e715a0ff91f9ba4d02c2227dff2 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Thu, 25 Apr 2019 16:41:01 +0200 Subject: [PATCH] Update I/O Port links in hardware interrupts post --- .../second-edition/posts/08-hardware-interrupts/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/content/second-edition/posts/08-hardware-interrupts/index.md b/blog/content/second-edition/posts/08-hardware-interrupts/index.md index 55739f2a..d8c8388b 100644 --- a/blog/content/second-edition/posts/08-hardware-interrupts/index.md +++ b/blog/content/second-edition/posts/08-hardware-interrupts/index.md @@ -66,7 +66,7 @@ This graphic shows the typical assignment of interrupt lines. We see that most o Each controller can be configured through two [I/O ports], one “command” port and one “data” port. For the primary controller these ports are `0x20` (command) and `0x21` (data). For the secondary controller they are `0xa0` (command) and `0xa1` (data). For more information on how the PICs can be configured see the [article on osdev.org]. -[I/O ports]: ./second-edition/posts/05-integration-tests/index.md#port-i-o +[I/O ports]: ./second-edition/posts/04-testing/index.md#i-o-ports [article on osdev.org]: https://wiki.osdev.org/8259_PIC ### Implementation @@ -497,7 +497,7 @@ We now see that a `k` appears on the screen when we press a key. However, this o To find out _which_ key was pressed, we need to query the keyboard controller. We do this by reading from the data port of the PS/2 controller, which is the [I/O port] with number `0x60`: -[I/O port]: ./second-edition/posts/05-integration-tests/index.md#port-i-o +[I/O port]: ./second-edition/posts/04-testing/index.md#i-o-ports ```rust // in src/interrupts.rs