public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shea Levy <shea@shealevy.com>
To: linux-kernel@vger.kernel.org
Subject: EFI Boot Stub on Removable Media
Date: Fri, 16 Mar 2012 15:30:24 -0400	[thread overview]
Message-ID: <4F6394D0.3090104@shealevy.com> (raw)

Hello,

I am currently working on making the live CDs for the NixOS distribution 
EFI-bootable with the EFI boot stub as the bootloader. Is there a 
recommended way to use a boot-stub enabled kernel on a removable device 
(where, AFAIK, there is no way to tell the firmware what params to boot 
with automatically)? Currently, I'm hacking together a really 
quick-and-dirty UEFI application that reads a parameters file at a 
pre-defined location and loads the kernel with those parameters, but I'd 
love a better alternative. Is it possible to embed an initrd in a 
bzImage after the image is built? Or is there some way to have a CD tell 
the firmware what arguments to pass to \EFI\BOOT\BOOT{ARCH}.EFI? Or some 
easy tweak to the kernel source to have it use a set of default 
parameters in absence of explicitly passed ones?

Cheers,
Shea Levy

                 reply	other threads:[~2012-03-16 19:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F6394D0.3090104@shealevy.com \
    --to=shea@shealevy.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox