Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Gummiboot fixup
Date: Wed, 20 Mar 2019 17:30:28 +0100	[thread overview]
Message-ID: <87sgvhcxuj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOR3GqV69iT1+1Qh3=j8MQygZGJApomnqB_xi1Hue3NrTRVTDA@mail.gmail.com> (Esben Haabendal's message of "Wed, 20 Mar 2019 16:03:16 +0100")

>>>>> "Esben" == Esben Haabendal <esbenhaabendal@gmail.com> writes:

 > Yes, you can use initrd=... if you provide the cmdline to the EFI stub.
 > But if you compile in the cmdline using CONFIG_CMDLINE, it will
 > not work, as it will only be available for Linux kernel, and not for
 > EFI stub.

I guess Even with CONFIG_CMDLINE, you could configure the boot entry to
pass initrd= to EFI, but OK.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2019-03-20 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 11:28 [Buildroot] [PATCH 0/3] Gummiboot fixup Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 1/3] gummiboot: use new official upstream git repository Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 2/3] gummiboot: upgrade to last commit before being removed Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 3/3] gummiboot: fix compatibility with newer glibc versions Esben Haabendal
2019-03-19 21:02   ` Thomas Petazzoni
2019-03-19 18:56 ` [Buildroot] [PATCH 0/3] Gummiboot fixup Peter Korsgaard
     [not found]   ` <CAOR3GqXSxZw3m+OD3FLCFOR0Gi-v3zNJGe2+3Bhy7R6av7LVhQ@mail.gmail.com>
2019-03-20 13:46     ` Peter Korsgaard
     [not found]       ` <CAOR3GqU17TUskOwG_8DfwrcEt_AJcqzgD8=5j1c2Wa+LVveeSg@mail.gmail.com>
2019-03-20 14:36         ` Peter Korsgaard
2019-03-20 15:03           ` Esben Haabendal
2019-03-20 16:30             ` Peter Korsgaard [this message]

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=87sgvhcxuj.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox