bee_vik

The saddest part about this is that it's the opposite of what Apple originally stood for. With the Apple II line, Apple released schematics and extraordinarily detailed technical reference manuals. Everything about the inner workings of those computers was an open book. Their motherboards were covered in chip sockets so you could replace nearly every component, and peripheral cards could be slotted in at will. It was a hobbyist's dream computer.

Granted, computers have changed a lot in the intervening years, but it still makes me sad to compare what Apple was to what Apple became.

I created a docker container that hosts the gcc cross-compiler I used to build my own OS:

https://hub.docker.com/r/brett/gcc-cross-x86_64-elf/

It hosts the gcc 7.1 x86_64-elf compiler with redzone disabled.

If you don't want to use the docker container, you can view the dockerfile to see the steps required to build the cross-compiler yourself:

https://github.com/beevik/docker/tree/master/gcc-cross-x86_6...

One resource I found myself consulting over and over again was the Intel Architecture Software Development manuals (https://software.intel.com/en-us/articles/intel-sdm). They're huge and obviously a bit dry, but they had about 90% of what I needed to know about x86 memory architecture and interrupts.

I included some other resources I consulted in the README. The OSDev wiki (http://wiki.osdev.org/Main_Page) is also good, although I found some of it to be dated or incorrect.

Good luck on developing your OS. Even though I'm not finished, it's been an extraordinarily valuable and educational process.

I'm part-way through my implementation of an x86_64 experimental OS and had to address all the issues you're facing right now. I didn't really document my process, but the code to get everything booted into x64 mode is there, including setting up the TSS.

https://github.com/beevik/MonkOS

In particular, the bootloader:

https://github.com/beevik/MonkOS/blob/master/boot/loader.asm