Comments (5)
Thanks for your detailed comments! I am travelling this weekend, but will address them as soon as I return on Monday 🙂
from rpi4-osdev.
Actually, I have just discovered the source of my confusion... google actually threw me on to the second page of the tutorial (which is confusingly called "part 1").
However, after reading the github Readme.md I realised that there is actually a page prior to that, which on the website can only be accessed (from the part one page) by changing the URL in the browser to https://www.rpi4os.com/. So this index page is (effectively) part zero (or introduction) - which equivalent to the README.md
. On this introduction page, I can now see the lines:
Hook up your RPi4 and make sure it boots into Raspbian. There are plenty of resources online to help you achieve/troubleshoot this. Getting Raspbian up will test that your hardware setup is working properly. Note: because I connected my RPi4 to my (not brilliant) TV, I needed to make an edit in the config.txt file on the SD card (setting the
hdmi_safe
parameter to 1) to ensure that I could see the screen. Without that, it was just black.
So, the confusion is basically due to fact that the part one page on the website (not the github site) not having any indication that there actually is a previous page before the part 1 page (there is no "previous page" link, or "back"/"back to part zero"/"back to introduction" link)... if that makes sense.
This confusion is compounded by google throwing visitors on to the part one page, rather than the part zero (or "introductory") page.
Possible fixes:
- Add a page 2 of 15 indicator somewhere on the part one page (as well as the other pages with the correspondingly correct page numbers used)
- Add a back to previous page link somewhere on the pages after the introduction (or part zero) page
- Renumber the parts so part one is actually part two (which would/could/might be a pain to implement)
- Something else I haven't thought of
Hopefully all of that makes sense. And apologies for having to complain about a beautifully written tutorial.
from rpi4-osdev.
it might be worth converting hdmi_safe
to combine it with a direct link to the RPi docs page, as there are some other things you can do in config.txt
that are specific to getting an acceptable TV output (and are referenced on those pages), but dont warrant further comment in the tutorial.
EDIT: haha :) when I first went to review this on the web url (not github) I could not find the link to the next page :)
from rpi4-osdev.
@paulwratt Good suggestion, and I've updated the intro to include a link to the further video options.
To the wider issue, I'm still pondering what the right approach to backlinking etc. is... 🤔
from rpi4-osdev.
OK, temporary fix done to add a link back to the intro from part1. It doesn't solve the problem if you land on part14, for example, (Google has indexed all parts), so definitely something to think about more as I go on. I suspect a ToC would be useful if I could add it non-intrusively on each part...
from rpi4-osdev.
Related Issues (20)
- Will this tutorial work for Raspberry Pi 1 Model B (512MB RAM) HOT 1
- Error with Makefile on Windows HOT 5
- Makefile path to LLVM differs HOT 2
- Typo - part 8 - "very my" HOT 2
- Typo - part 9 - "hz" HOT 4
- Link - part 11 - Not hypertext HOT 1
- Page number - part 14 - Incorrect page reference on datasheet HOT 1
- Explanation - part 14 - Active LOW HOT 1
- Typo - Part 14 - arp.c - random close comment HOT 1
- Raspberry Pi 4 kernel load address HOT 2
- Building to test on QEMU/KVM HOT 4
- Improve framebuffer drawing -- dual buffering or other technique? HOT 1
- Synchronous Exception at mmio_write() HOT 4
- External vs internal ethernet controller HOT 1
- Where is this stuff documented? HOT 1
- "Incorrect" mailbox protocol in part 5 HOT 2
- Question: USB Support HOT 12
- Timer 3 bar not fully painted in Part 13 (Interrupts) HOT 10
- Pull Up Pull down register is the wrong way around HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rpi4-osdev.