Documentation: Fix remaining typoes "persistant", "existance".
Subsystems (5)
Documentation Arm (32-bit) Arm i.MX and Layerscape Memory technology devices (MTD) +1 more subsystems
PATCH 1/1 Documentation: Fix remaining typoes "persistant", "existance".
Fix a couple typoes that occur only in Documentation/ or in comments, so no functional change.
Signed-off-by Robert P. J. Day <[email protected]>
---
Documentation/boards/mxs/Chumby-Falconwing.rst +1 -1
@@ -36,7 +36,7 @@ How to prepare an MCI card to boot the "chumby one" with barebox * Create four primary partitions on the MCI card * the first one for the bootlets (about 256 kiB) - * the second one for the persistant environment (size is up to you, at least 256k) + * the second one for the persistent environment (size is up to you, at least 256k) * the third one for the kernel (2 MiB ... 4 MiB in size) * the fourth one for the root filesystem which can fill the rest of the available space
Documentation/boards/x86.rst +7 -7
@@ -32,7 +32,7 @@ prepared in some special way: the first partition must start at a sector behind the ones barebox occupies. * barebox handles its runtime configuration in a special way: It - stores it in a binary way into some reserved sectors ("persistant + stores it in a binary way into some reserved sectors ("persistent storage"). Boot Preparations
@@ -52,12 +52,12 @@ simple calulation:: sectors = (\<size of barebox image\> + 511) / 512 To be able to store the runtime configuration, further free sectors are -required. Its up to you and your requirements, how large this persistant +required. Its up to you and your requirements, how large this persistent storage must be. If you need 16 kiB for this purpose, you need to keep additional 32 sectors free. For this example we are reserving 300 sectors for the barebox image and -additionaly 32 sectors for the persistant storage. So, the first partition on +additionaly 32 sectors for the persistent storage. So, the first partition on the boot media must start at sector 333 or later. Run the fdisk tool to setup such a partition table::
@@ -116,18 +116,18 @@ In the next step, barebox gets installed to this boot media:: This command writes the barebox image file './barebox' onto the device /dev/sda. -The -s option will keep the persistant storage sectors free and untouched -and set flags in the MBR to forward its existance, size and location to +The -s option will keep the persistent storage sectors free and untouched +and set flags in the MBR to forward its existence, size and location to barebox at runtime. setupmbr also does not change the partition table. The barebox image gets stored on the boot media like this:: sector 0 1 33 333 |---|-------------|--------------- ~~~ ------------|-------------- - MBR persistant barebox first + MBR persistent barebox first storage main image partition -If the -s option is omitted, the "persistant storage" part simply does +If the -s option is omitted, the "persistent storage" part simply does not exist:: sector 0 1 333
arch/arm/boards/karo-tx28/tx28-stk5.c +1 -1
@@ -311,7 +311,7 @@ static const uint32_t tx28_starterkit_pad_setup[] = {* Try to register an environment storage on the attached MCI card * @return 0 on success * -* We rely on the existance of a usable SD card, already attached to +* We rely on the existence of a usable SD card, already attached to * our system, to get a persistent memory for our environment. * If this SD card is also the boot medium, we can use the second partition * for our environment purpose (if present!).
drivers/mtd/nand/nomadik_nand.c +1 -1
@@ -214,7 +214,7 @@ static int nomadik_nand_probe(struct device_d *dev) nand->options = pdata->options;/* -* Scan to find existance of the device +* Scan to find existence of the device */ if (nand_scan (&host->mtd,1 )) { ret = -ENXIO ;
scripts/setupmbr/setupmbr.c +1 -1
@@ -673,7 +673,7 @@ This command writes the @a barebox image file './barebox.bin' onto the device @p /dev/sda. The @p -s option will keep the persistent storage sectors free and untouched -and set flags in the MBR to forward its existance, size and location to +and set flags in the MBR to forward its existence, size and location to @a barebox at runtime. @p setupmbr also does not change the partition table. The @a barebox image gets stored on the boot media like this:
Signature · 12 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/bareboxSascha Hauer
maintainerQuoted 5 lines · Robert P. J. Day
Fix a couple typoes that occur only in
Documentation/or in comments, so no functional change.Signed-off-by Robert P. J. Day <[email protected]>
I'll apply this one after I have merged the different for-next topics into master the next time.
Sascha
Quoted 122 lines
---
Documentation/boards/mxs/Chumby-Falconwing.rst +1
-1@@ -36,7 +36,7 @@ How to prepare an MCI card to boot the "chumby one" with barebox * Create four primary partitions on the MCI card * the first one for the bootlets (about 256 kiB) - * the second one for the persistant environment (size is up to you, at least 256k) + * the second one for the persistent environment (size is up to you, at least 256k) * the third one for the kernel (2 MiB ... 4 MiB in size) * the fourth one for the root filesystem which can fill the rest of the available spaceDocumentation/boards/x86.rst +7
-7@@ -32,7 +32,7 @@ prepared in some special way: the first partition must start at a sector behind the ones barebox occupies. * barebox handles its runtime configuration in a special way: It - stores it in a binary way into some reserved sectors ("persistant + stores it in a binary way into some reserved sectors ("persistent storage"). Boot Preparations@@ -52,12 +52,12 @@ simple calulation:: sectors = (\<size of barebox image\> + 511) / 512 To be able to store the runtime configuration, further free sectors are -required. Its up to you and your requirements, how large this persistant +required. Its up to you and your requirements, how large this persistent storage must be. If you need 16 kiB for this purpose, you need to keep additional 32 sectors free. For this example we are reserving 300 sectors for the barebox image and -additionaly 32 sectors for the persistant storage. So, the first partition on +additionaly 32 sectors for the persistent storage. So, the first partition on the boot media must start at sector 333 or later. Run the fdisk tool to setup such a partition table::@@ -116,18 +116,18 @@ In the next step, barebox gets installed to this boot media:: This command writes the barebox image file './barebox' onto the device /dev/sda. -The -s option will keep the persistant storage sectors free and untouched -and set flags in the MBR to forward its existance, size and location to +The -s option will keep the persistent storage sectors free and untouched +and set flags in the MBR to forward its existence, size and location to barebox at runtime. setupmbr also does not change the partition table. The barebox image gets stored on the boot media like this:: sector 0 1 33 333 |---|-------------|--------------- ~~~ ------------|-------------- - MBR persistant barebox first + MBR persistent barebox first storage main image partition -If the -s option is omitted, the "persistant storage" part simply does +If the -s option is omitted, the "persistent storage" part simply does not exist:: sector 0 1 333arch/arm/boards/karo-tx28/tx28-stk5.c +1
-1@@ -311,7 +311,7 @@ static const uint32_t tx28_starterkit_pad_setup[] = {* Try to register an environment storage on the attached MCI card * @return 0 on success * -* We rely on the existance of a usable SD card, already attached to +* We rely on the existence of a usable SD card, already attached to * our system, to get a persistent memory for our environment. * If this SD card is also the boot medium, we can use the second partition * for our environment purpose (if present!). drivers/mtd/nand/nomadik_nand.c +1
-1@@ -214,7 +214,7 @@ static int nomadik_nand_probe(struct device_d *dev) nand->options = pdata->options;/* -* Scan to find existance of the device +* Scan to find existence of the device */ if (nand_scan (&host->mtd,1 )) { ret = -ENXIO ;scripts/setupmbr/setupmbr.c +1
-1@@ -673,7 +673,7 @@ This command writes the @a barebox image file './barebox.bin' onto the device @p /dev/sda. The @p -s option will keep the persistent storage sectors free and untouched -and set flags in the MBR to forward its existance, size and location to +and set flags in the MBR to forward its existence, size and location to @a barebox at runtime. @p setupmbr also does not change the partition table. The @a barebox image gets stored on the boot media like this:Signature · 14 lines
-- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox