Let’s write a Kernel with keyboard and screen support (2014)

If anyone wants to breach into kernel development, I recommend osdev[0], which is a very good resources for beginners and others.<p>0: <a href="https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Main_Page" rel="nofollow">https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Main_Page</a>

Build a custom&#x2F;weird CPU: <a href="https:&#x2F;&#x2F;cpudev.org&#x2F;wiki&#x2F;Main_Page" rel="nofollow">https:&#x2F;&#x2F;cpudev.org&#x2F;wiki&#x2F;Main_Page</a> and write an OS for it: <a href="https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Main_Page" rel="nofollow">https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Main_Page</a><p>I know what I&#x27;m gonna do this winter :P

This is making me wonder: Thinking about Dan Luu&#x27;s research on latency of modern systems (<a href="https:&#x2F;&#x2F;danluu.com&#x2F;input-lag&#x2F;" rel="nofollow">https:&#x2F;&#x2F;danluu.com&#x2F;input-lag&#x2F;</a>), what is the minimum latency one could get in a modern system (e.g, USB keyboard, modern display hardware)?

I hate to sound dismissive but I feel like a lot of these projects put too much emphasis on booting and too little on something like say process semantics. I&#x27;ve written bootloaders before and it was some of the most uninspired code I&#x27;ve ever written.

For further reading, I can&#x27;t recommend enough this free book:<p><a href="http:&#x2F;&#x2F;pages.cs.wisc.edu&#x2F;~remzi&#x2F;OSTEP&#x2F;" rel="nofollow">http:&#x2F;&#x2F;pages.cs.wisc.edu&#x2F;~remzi&#x2F;OSTEP&#x2F;</a><p>It&#x27;s fantastically well-written, yet detailed without being overwhelming.

This is not yet a kernel. This is code booting into protected mode and handling some interrupts.

x86 16-bit real mode! It&#x27;s certainly easy, but only because all the real work (initialising the PCI bus to speak to the video card, USB host drivers for the keyboard) is being done by the BIOS somewhere.<p>Does anyone know these days if the 16-bit boot environment is still &quot;bare metal&quot;, or is it inside an UEFI or ACPI hypervisor of some sort?

I&#x27;ve not watched the series, but the full stack (ie. Cpu and gpu design in verilog, hdmi, bootstrapped mutitasking os dev, not your average FullStack marketing-speak) for a platform is done by bitwise: <a href="https:&#x2F;&#x2F;m.youtube.com&#x2F;#&#x2F;user&#x2F;pervognsen" rel="nofollow">https:&#x2F;&#x2F;m.youtube.com&#x2F;#&#x2F;user&#x2F;pervognsen</a><p>Looks very accessible :)

I may be wrong, but if you assume a non-ancient x86 platform with EFI BIOS, don’t you get all this for free from drivers included in EFI?

640 x 480, 16 colors, ring 0