On Thu, Nov 14, 2019 at 12:56:25PM +0200, Toomas Soome via Grub-devel wrote: > > On 14. Nov 2019, at 12:27, Max Tottenham via Grub-devel > > <grub-devel@gnu.org> wrote: > > On 10/28, Daniel Kiper wrote: > >> Hi Max, > > > > ... > > > >> Yeah, I think you are right. Additionally, please take a look at [1] and > >> especially at [2]. The series is about to commit and setup_indirect part > >> can be very useful for you. And I would like to see similar feature in the > >> Multiboot2 protocol [3]. > > > > So it looks to me like setup_data is linux specific, which is fine for > > me, but would mean that the BSDs wouldn't be able to take advantage of > > some more generic bootloader <-> userspace interface (like a file in a > > ramdisk). > > multiboot2 already does have modules mechanism, which is pretty > generic because the identification can be done via module command > line. > > For example, for illumos we are providing boot loader environment > variables as module (commandline) type=environment, console font as > type=console-font and so on.
This is another option but I prefer to have separate Multiboot2 type for "log" thing. This way we will not confuse existing users of module Multiboot2 type. Daniel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
