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

Changed Github username

Browse source
This commit is contained in:
babbleberry 2024-01-26 22:16:28 +00:00
parent 5166f343e3
commit 753489b857
5 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/FUNDING.yml vendored
View file

@ -1 +1 @@
github: isometimes github: babbleberry

2
RPI-BUILD.md
View file

@ -23,7 +23,7 @@ Note: you can avoid re-imaging the Pi, by instead [building a cross-compiler you
Now let's build something: Now let's build something:
* Use `git` to clone this repo: `git clone https://github.com/isometimes/rpi4-osdev.git` * Use `git` to clone this repo: `git clone https://github.com/babbleberry/rpi4-osdev.git`
* Decide which part you want to build - I like testing with _part5-framebuffer_ (it's visual, so you'll know when it works!) * Decide which part you want to build - I like testing with _part5-framebuffer_ (it's visual, so you'll know when it works!)
* Copy the _Makefile.gcc_ to _Makefile_ * Copy the _Makefile.gcc_ to _Makefile_
* Edit the _Makefile_ and ensure the `GCCPATH` variable points to the _bin_ subdirectory where your cross-compiler is to be found * Edit the _Makefile_ and ensure the `GCCPATH` variable points to the _bin_ subdirectory where your cross-compiler is to be found

2
_config.yml
View file

@ -1,4 +1,4 @@
remote_theme: isometimes/cayman-ga4 remote_theme: babbleberry/cayman-ga4
google_analytics: G-YL02TRV3C8 google_analytics: G-YL02TRV3C8
url: "https://www.rpi4os.com" url: "https://www.rpi4os.com"
plugins: plugins:

2
part15-tcpip-webserver/README.md
View file

@ -86,7 +86,7 @@ We then serve responses based on three possible cases:
* The incoming request is not a GET request (eg. maybe it's a HEAD request) - you can simulate this using the `curl` tool: `curl -I 192.168.0.66` * The incoming request is not a GET request (eg. maybe it's a HEAD request) - you can simulate this using the `curl` tool: `curl -I 192.168.0.66`
* The incoming request is a GET request for the root web page `/` - `curl 192.168.0.66/` * The incoming request is a GET request for the root web page `/` - `curl 192.168.0.66/`
* The incoming request is a GET request for any non-root web page - eg. `curl 192.168.0.66/isometimes/monkey` * The incoming request is a GET request for any non-root web page - eg. `curl 192.168.0.66/babbleberry/monkey`
I recommend reading [this page](http://tuxgraphics.org/electronics/200905/embedded-tcp-ip-stack.shtml) for a full explanation. The code I have ported is very similar to what you see there. I recommend reading [this page](http://tuxgraphics.org/electronics/200905/embedded-tcp-ip-stack.shtml) for a full explanation. The code I have ported is very similar to what you see there.

2
part6-breakout/README.md
View file

@ -150,7 +150,7 @@ 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!_
PS: if you have issues using the Arm gcc compiler (namely an unexpected crash after painting the first brick), you might to try setting the compiler optimisation level to `-O1` instead of `-O2` in the _Makefile_. Some folks have [reported issues](https://github.com/isometimes/rpi4-osdev/issues/17), and I am able to reproduce these. PS: if you have issues using the Arm gcc compiler (namely an unexpected crash after painting the first brick), you might to try setting the compiler optimisation level to `-O1` instead of `-O2` in the _Makefile_. Some folks have [reported issues](https://github.com/babbleberry/rpi4-osdev/issues/17), and I am able to reproduce these.
![The finished game](images/6-breakout-thefinishedgame.jpg) ![The finished game](images/6-breakout-thefinishedgame.jpg)