mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH] Documentation: efi: add example how to create EFI partition
Date: Wed,  6 Sep 2017 14:11:06 +0200	[thread overview]
Message-ID: <20170906121106.26024-1-linux@rempel-privat.de> (raw)

From: Oleksij Rempel <o.rempel@pengutronix.de>

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
 Documentation/boards/efi.rst | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index 8f78a800e..6c90e6cdf 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -47,6 +47,31 @@ has to be put into the ``EFI/barebox/`` directory.
 Supported backends for EFI are raw partitions that can be discovered via a
 partition UUID.
 
+With this sample script you can create bootable image and transfer it to the
+flash driver:
+
+.. code-block:: sh
+
+  truncate --size 128M barebox-boot.img
+  echo 'start=2048, type=ef' | sfdisk barebox-boot.img
+
+  LOOPDEV=$(losetup --find --show barebox-boot.img)
+  partprobe ${LOOPDEV}
+
+  # Create filesystems
+  mkfs.fat -F32 ${LOOPDEV}p1
+  MOUNTDIR=$(mktemp -d -t demoXXXXXX)
+  mount ${LOOPDEV}p1 $MOUNTDIR
+  mkdir -p ${MOUNTDIR}/EFI/BOOT/
+  cp barebox.efi ${MOUNTDIR}/EFI/BOOT/BOOTx64.EFI
+  if [ -d network-drivers ]; then
+    cp -r network-drivers ${MOUNTDIR}/
+  fi
+  umount ${MOUNTDIR}
+  losetup -d ${LOOPDEV}
+
+  dd if=barebox-boot.img of=/dev/sdX
+
 Running EFI barebox on qemu
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-- 
2.11.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2017-09-06 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 12:11 Oleksij Rempel [this message]
2017-09-08  6:19 ` Sascha Hauer

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=20170906121106.26024-1-linux@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=barebox@lists.infradead.org \
    --cc=o.rempel@pengutronix.de \
    /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