suspended due to lost of all the target park boards (russians destroyed our town). look forward, not backward.Įfify - UEFI for a couple of boards (mips and arm). again, it's a bad idea to make your kernel a plain dumb binary messing up with dinosauric BIOS calls. also you could use third party loaders like grub or whatever and follow their conventions on loading your kernel. something similar should be possible for x86 I guess. I make it an elf file first, because my tools only speak elf, >_> and then translate it into a plain binary with the objcopy uitility. I am not messing around with x86, but I have similar needs - I have ROM code which wants a plain binary (my code) at the sector 1 of a storage, it loads it and jumps to it. you've been already adviced above as to what you should do and use. make your boot loader suitable for interacting with BIOS not OS.
It's basically wrong to glue your OS with BIOS directly, unless you are writing some dinosaurOS Make your OS a formatted executable (elf, pe/coff) and make your bootloader load it properly. However, I want to make it suitable for my OS.
Do I have to change anything? I want to play with 0xb800 in C. Learn? How do I make GCC compile my C for my OS? I don't think you can't boot an ELF binary with INT 13h.
