jordan/rpi4-osdev
1
0
Fork 0
mirror of https://github.com/isometimes/rpi4-osdev synced 2024-11-09 20:00:40 +00:00
Code Issues Projects Releases Packages Wiki Activity

Added crosslinks in Markdown for Pages

Browse source
This commit is contained in:
Adam Greenwood-Byrne 2020-07-27 18:46:39 +01:00
parent e75b3afe96
commit b13b086099
5 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
part2-building/README.md
View file

@ -68,3 +68,5 @@ _You've just booted your very own OS!_
As exciting as that sounds, all you're likely to see after the RPi4's own "rainbow splash screen" is an empty, black screen. However, we shouldn't be so surprised: we haven't yet asked it to do anything other than spin in an infinite loop. As exciting as that sounds, all you're likely to see after the RPi4's own "rainbow splash screen" is an empty, black screen. However, we shouldn't be so surprised: we haven't yet asked it to do anything other than spin in an infinite loop.
The foundations are laid though, and we can start to do exciting things now. **Congratulations for getting this far!** The foundations are laid though, and we can start to do exciting things now. **Congratulations for getting this far!**
[Go to part3-helloworld >](../part3-helloworld)

2
part3-helloworld/README.md
View file

@ -215,3 +215,5 @@ Then:
If you've followed all these instructions, after a few seconds you'll see "Hello world!" appear in your PuTTY window on your dev machine. If you've followed all these instructions, after a few seconds you'll see "Hello world!" appear in your PuTTY window on your dev machine.
_It's a message from your RPi4 to say that your OS is working. Proof at last!_ _It's a message from your RPi4 to say that your OS is working. Proof at last!_
[Go to part4-miniuart >](../part4-miniuart)

2
part4-miniuart/README.md
View file

@ -65,3 +65,5 @@ We can now read from our UART too! If you build the kernel and power on the RPi4
_Now we're communicating in two directions!_ _Now we're communicating in two directions!_
We also implemented a software [FIFO buffer](https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics)) for our UART communication. The RPi4 has limited buffer space for data arriving on the UART, and incorporating our own is likely to make it easier to manage incoming data in future. We also implemented a software [FIFO buffer](https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics)) for our UART communication. The RPi4 has limited buffer space for data arriving on the UART, and incorporating our own is likely to make it easier to manage incoming data in future.
[Go to part5-framebuffer >](../part5-framebuffer)

2
part5-framebuffer/README.md
View file

@ -154,3 +154,5 @@ Now fire up the RPi4!
_We've done so much more than a basic "Hello world!" on-screen already!_ Sit back, relax and enjoy your artwork. In the next tutorial, we'll be combining graphics with keyboard input from the UART to create our first game. _We've done so much more than a basic "Hello world!" on-screen already!_ Sit back, relax and enjoy your artwork. In the next tutorial, we'll be combining graphics with keyboard input from the UART to create our first game.
![Our first on-screen artwork](images/5-framebuffer-screen.jpg) ![Our first on-screen artwork](images/5-framebuffer-screen.jpg)
[Go to part6-breakout >](../part6-breakout)

2
part6-breakout/README.md
View file

@ -149,3 +149,5 @@ I hope writing your first game was easier than you thought it might be - and on
_Well done, you've just written your first game!_ _Well done, you've just written your first game!_
![The finished game](images/6-breakout-thefinishedgame.jpg) ![The finished game](images/6-breakout-thefinishedgame.jpg)
[Go to part7-bluetooth >](../part7-bluetooth)