Am 14/01/2013 10:47, schrieb Fredrik Holmqvist:
2013/1/14 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:I can't see why haiku_loader should not be the EFI application, or how your way can be any easier than this one. But maybe you can enlighten me :-) AFAICT the point of gnu-efi is to let you compile EFI apps from Linux without headaches as well.Me neither, except for all the work needed. We have a few options though. The big issue is EFI can't read BFS, so we need to move haiku_loader from the partition to the EFI system partition or create another EFI app that find and loads haiku_loader. I prefer the latter as we can have different version of haiku and loaders more easily.
That doesn't really make any sense to me.If you have an extra EFI loader that "just" loads the haiku_loader you are essentially duplicating the haiku_loader. It's not just BFS access, there also can be any number of Haiku installations around, so you would even have to provide a menu to choose the partition to boot from. The boot loader - kernel handshake is supposed to be stable at one point (R1), and will remain backwards compatible, so having different haiku_loaders around should not be problematic at all.
Furthermore, you'll have to use all those EFI APIs there, anyway.Writing an EFI backend for the haiku_loader should be relatively simple, and straight-forward, as it already implements all the functionality you'll need. The hardest thing will probably be to build a proper EFI executable, and integrate this with our build system.
Bye, Axel.
