From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: "Stoppa, Igor" <igor.stoppa-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [x86] [EFI stub] Changing the kernel command line in the efi application, without recompiling the kernel.
Date: Mon, 16 Nov 2015 09:30:41 +0000 [thread overview]
Message-ID: <20151116093041.GA2817@codeblueprint.co.uk> (raw)
In-Reply-To: <CAC_FEN0qfR47ST4xewf2hc7vgH7eNm1_d-K-ZMwJWd-yNo58jg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 04 Nov, at 01:35:16PM, Stoppa, Igor wrote:
> Hi,
>
> I'm currently building a combo efi application comprised of
>
> * uefi stub from gummiboot
> * linux kernel
> * kernel command line
> * microcode + initramfs
>
> using the approach from mkrescue-uefi.sh [1]
>
> However I'd like to replace the gummiboot stub with the one coming
> with the kernel, and get rid of one dependency (gummiboot).
> But it seems that the command line is handled differently:
>
> * in the gummiboot way I can change the command line without having to
> recompile the kernel, because it is contained in a separate section of
> the application.
>
> * in the kernel-only way, it is contained in the field "load_options"
> from efi_loaded_image_t [2]
> So for what I can understand, I would have to rebuild the kernel, to
> change the command line of the combo application.
>
>
> Is that correct?
Nope, you don't need to rebuild your kernel image. You can simply
change the paramters passed in your EFI BootXXXX variable by the EFI
boot manager, see efibootmgr(8).
However, if you're not using the load options argument and instead are
relying on CONFG_CMDLINE, then yes, you will need to rebuild your
kernel.
prev parent reply other threads:[~2015-11-16 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:35 [x86] [EFI stub] Changing the kernel command line in the efi application, without recompiling the kernel Stoppa, Igor
[not found] ` <CAC_FEN0qfR47ST4xewf2hc7vgH7eNm1_d-K-ZMwJWd-yNo58jg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-16 9:30 ` Matt Fleming [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=20151116093041.GA2817@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=igor.stoppa-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).