You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A glaring flaw is the lack of a 512b minimal bootloader that ATA loads the kernel to its dest and then enters protected and jumps to _start. One reason to add one is the extra swag of having very very tiny kernels that still can do stuff.
Several problems:
Theres not enough room to really inspect ELFs and validate stuff, GRUB will at least tell you if something is wrong even if its a big blob. So, either the bootloader just jumps to <some offset in the ELF that corresponds to the 64-bit program entry>, or we need to burn the _start location into the bootloader itself via a script.
We no longer get memory maps from GRUB so we have to do without. CMOS chip will tell us about up to 64mb of memory, which is basically nothing today. It really is a problem.
It will likely be brittle on real hardware - especially the ATA loader code. It also won't work on modern clouds like GCE which demands you boot using virtio-scsi.
In short, it may just not be worth it.
The text was updated successfully, but these errors were encountered:
A glaring flaw is the lack of a 512b minimal bootloader that ATA loads the kernel to its dest and then enters protected and jumps to _start. One reason to add one is the extra swag of having very very tiny kernels that still can do stuff.
Several problems:
In short, it may just not be worth it.
The text was updated successfully, but these errors were encountered: