281–282 of 282 posts
(Waiting for page to load) "Nice, so they finally got a kernel to boot. I wonder what fancy way they'll be showing the dmesg infor--" "Oh." I think I need to recalibrate my idea of a 10x developer... (The standard would seem to have ratcheted up somewhat as the years have gone by!)
Note that this team already ported Linux to the iPhone, so what they did recently was update their iPhone port to support M1.
Earlier quoted context omitted.
1. Accept that printf (preferably over serial) is The One True Debugger. It is the tool you always have - if you can't get a print over serial, you're in too deep to use a debugger anyway. 2. Play around with embedded. You can use an arduino, but get rid of the Arduino IDE. Once you've ridded yourself from their weird environment and code in C, you're pretty close to what kernel programming is: Direct hardware contro…
I got to build a driver once, making an NDIS LWF encap/decap driver for Windows. I found it extremely soothing, and kind of old school - I had to use a real machine in my office with firewire debugging, and use windbg like a greybeard. But not having the right documentation was a challenge. MSDN is okay, but the weird mechanics of MDL chains don't really get discussed on Stack Overflow.
How do people overcome this? I managed to reverse my laptop's LED commands: they were implemented via USB so I used wireshark to intercept and analyze the data sent by the proprietary vendor software. What if it's some ACPI thing though? Or some memory mapped I/O chip? How do people figure out how it works?