From: Greg KH <greg@kroah.com>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
kernelnewbies@kernelnewbies.org
Subject: Re: efivars
Date: Thu, 23 Sep 2021 07:41:34 +0200 [thread overview]
Message-ID: <YUwTjkVCEvTjFhD2@kroah.com> (raw)
In-Reply-To: <8e7ea1b5-c74b-584f-5d06-20973de89f77@mrbrklyn.com>
On Wed, Sep 22, 2021 at 10:02:43PM -0400, Ruben Safir wrote:
> On 9/22/21 1:04 PM, Valdis Klētnieks wrote:
> > 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.
>
>
> Link?
>
> FWIW, it doesn't need anything from the boot loader. The installed OS
> is capable of IDing hardware and running.
How does the OS determine something as "simple" as "where is the memory
in the system" without getting that information from the bootloader?
How does the hardware describe itself to the OS?
> I've read through the entire documantation for UEFI, as boring as that
> is never saw anyiong about passing info to the OS.
I think you missed some sections :)
> I did a sumation of this at one point:
>
> http://www.nylxs.com/docs/grad_school/uefi/page1.html
Private page :(
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-23 5:42 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 ` efivars Valdis Klētnieks
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 ` Greg KH [this message]
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=YUwTjkVCEvTjFhD2@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.com \
--cc=valdis.kletnieks@vt.edu \
/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.