From 9a45be2e6a6a48a2e96bc669bff3d1818ee85551 Mon Sep 17 00:00:00 2001 From: Frank Hunleth Date: Sat, 14 Dec 2024 14:19:07 -0500 Subject: [PATCH] Minor edits to MBR docs --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 61d6c756..6d7e5bee 100644 --- a/README.md +++ b/README.md @@ -428,8 +428,8 @@ Linux and the bootloaders for finding the file systems that exist on the media. In comparison to a tool like `fdisk`, `fwup` only supports simplistic partition setup, but this is sufficient for many devices. Tools such as `fdisk` can be used to determine the block offsets and sizes of partitions for the -configuration file. Offsets and sizes are given in 512 byte blocks. Here's a -potential mbr definition: +configuration file. Offsets and sizes are given in 512 byte blocks. Here's an +example mbr definition: ```conf mbr mbr-a { @@ -460,6 +460,8 @@ mbr mbr-a { } ``` +### OSIP + If you're using an Intel Edison or similar platform, `fwup` supports generation of the OSIP header in the MBR. This header provides information for where to load the bootloader (e.g.., U-Boot) in memory. The `include-osip` option @@ -493,6 +495,8 @@ mbr mbr-a { } ``` +### Expanding the final partition + Sometimes it's useful to have the final partition fill the remainder of the storage. This is needed if your target's storage size is unknown and you need to use as much of it as possible. The `expand` option requests that `fwup`