All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: Greg KH <greg@kroah.com>, kernelnewbies@kernelnewbies.org
Subject: Re: efivars
Date: Wed, 22 Sep 2021 13:04:40 -0400	[thread overview]
Message-ID: <163752.1632330280@turing-police> (raw)
In-Reply-To: <968231e8-69f3-872b-7451-4439744b2d4f@mrbrklyn.com>


[-- Attachment #1.1: Type: text/plain, Size: 1307 bytes --]

On Wed, 22 Sep 2021 11:58:55 -0400, Ruben Safir said:
> OS's shouldn't need anything from a boot loader.  That ties the OS to
> the bootloader completely without need.

You might want to read Documentation/x86/boot.rst and think about what  the OS
is expecting to get passed from the boot loader, and then think about how you
would deal with the situation if that information wasn't passed along.

And oddly enough, your OS isn't tied to the boot loader.  In fact, any of the
following will work:

  Assigned boot loader ids (hexadecimal):

        == =======================================
        0  LILO
           (0x00 reserved for pre-2.00 bootloader)
        1  Loadlin
        2  bootsect-loader
           (0x20, all other values reserved)
        3  Syslinux
        4  Etherboot/gPXE/iPXE
        5  ELILO
        7  GRUB
        8  U-Boot
        9  Xen
        A  Gujin
        B  Qemu
        C  Arcturus Networks uCbootloader
        D  kexec-tools
        E  Extended (see ext_loader_type)
        F  Special (0xFF = undefined)
        10 Reserved
        11 Minimal Linux Bootloader
           <http://sebastian-plotz.blogspot.de>
        12 OVMF UEFI virtualization stack
        == =======================================

And that's just the *documented* ones. So, as you were saying?


[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2021-09-22 17:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  6:22 efivars Ruben Safir
2021-09-22  6:35 ` efivars Greg KH
2021-09-22 15:47   ` efivars Ruben Safir
2021-09-22 16:07     ` efivars Greg KH
2021-09-23  4:01       ` efivars Ruben Safir
2021-09-23  9:56       ` efivars Ruben Safir
2021-09-23 10:10         ` efivars Greg KH
2021-09-23 10:28         ` efivars FMDF
2021-09-23 12:34           ` efivars Ruben Safir
2021-09-23 12:40           ` efivars Ruben Safir
2021-09-23 12:44           ` efivars Ruben Safir
2021-09-22 15:58   ` efivars Ruben Safir
2021-09-22 16:11     ` efivars Greg KH
2021-09-22 17:04     ` Valdis Klētnieks [this message]
2021-09-23  1:51       ` efivars Ruben Safir
2021-09-23  2:02       ` efivars Ruben Safir
2021-09-23  2:10         ` efivars Dave Stevens
2021-09-23  5:41         ` efivars Greg KH
2021-09-23  2:07       ` efivars Ruben Safir
2021-09-23  7:32         ` efivars Bjørn Mork
2021-09-23  8:41           ` efivars Ruben Safir
2021-09-23  8:57             ` efivars Greg KH
2021-09-23  8:12         ` efivars Valdis Klētnieks
2021-09-23  8:32           ` efivars Ruben Safir
2021-09-23  7:13     ` efivars Bjørn Mork
2021-09-23  9:17       ` efivars Ruben Safir
2021-09-23  9:39         ` efivars Greg KH
     [not found] ` <CAPj211tgoRDDsZA_1ZM-kWRiHM9r2MQVi5b-mQenpP8pQmfvXg@mail.gmail.com>
2021-09-22 15:56   ` efivars Ruben Safir
2021-09-23  7:11 ` efivars FMDF
2021-09-23  7:22   ` efivars FMDF
2021-09-23  7:27     ` efivars FMDF
2021-09-23 12:24       ` efivars Ruben Safir
2021-09-23 12:36         ` efivars Greg KH
2021-09-23  9:38   ` efivars Ruben Safir
2021-09-23  9:56     ` efivars Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=163752.1632330280@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=ruben@mrbrklyn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.