All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Borislav Petkov <bp@alien8.de>
Cc: hpa@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Jonathan Corbet <corbet@lwn.net>,
	barebox@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: x86: boot: reserve type_of_loader=13 for barebox
Date: Sun, 2 Oct 2022 09:15:09 +0200	[thread overview]
Message-ID: <5da3593c-1607-9075-e1ac-1e384fd62b93@pengutronix.de> (raw)
In-Reply-To: <YzjDHOWkIoWF+h/R@zn.tnic>

Hello,

On 02.10.22 00:45, Borislav Petkov wrote:
> On Fri, May 13, 2022 at 04:30:39PM +0200, Ahmad Fatoum wrote:
>> barebox built as EFI payload has been booting Linux on x86 with
>> type_of_loader=0xff since v2015.09.0.
> 
> What is barebox?
> 
> That https://en.wikipedia.org/wiki/Barebox ?

Yes.

> 
> That version number v2015 - am I to understand it that it has been
> booting Linux since the year 2015?
> 
> In any case, it would be useful to explain a bit what it is here.

Release cadence is monthly. Starting with release v2015.09.0,
type_of_loader=0xff was being used. I figured it's about time, we
allocate an ID for it.

> 
>> Reserve 13, the next free id, so this can be used instead.
> 
> Sure, I guess, why not.
> 
> Thx.
Cheers,
Ahmad


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-10-02  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 14:30 [PATCH] Documentation: x86: boot: reserve type_of_loader=13 for barebox Ahmad Fatoum
2022-05-13 14:30 ` Ahmad Fatoum
2022-10-01 22:45 ` Borislav Petkov
2022-10-02  7:15   ` Ahmad Fatoum [this message]
2022-10-02 11:29     ` Borislav Petkov

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=5da3593c-1607-9075-e1ac-1e384fd62b93@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.