From c718a582aa3545bb4ada7bafbd9467d9dbe1549a Mon Sep 17 00:00:00 2001 From: Le Minh Nghia Date: Mon, 1 Jan 2018 11:20:30 +0700 Subject: [PATCH] Update computer architecture image link --- Basic-Assembly-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Basic-Assembly-tutorial.md b/Basic-Assembly-tutorial.md index 21c3979..dc850d2 100644 --- a/Basic-Assembly-tutorial.md +++ b/Basic-Assembly-tutorial.md @@ -182,7 +182,7 @@ NOT 0011 1111 0000 1010 ## Computers and code ### Basic computer architecture Here is a basic diagram of the system design of a modern computer -![](https://github.com/simon987/Much-Assembly-Required-3/blob/master/Computer%20architecture.png?raw=true) +![](https://user-images.githubusercontent.com/13317164/34465589-8dbc9530-eee5-11e7-99cc-5ad3bd27ebec.png) We can see that all there is a lot of I/O (input and output) hardware connected to the CPU, but we don't really have to worry about the exact way to access these from within the CPU because it is taken care of by the operating system (Linux, Windows...). In the real world, programmers use **system calls** which are understood by the operating system to request access to certain files on the hard drive or to display text on the screen. Only the CPU, memory and registers (in green) are relevant for the game.