summaryrefslogtreecommitdiffstats
path: root/Documentation/boards
diff options
context:
space:
mode:
authorWadim Egorov <w.egorov@phytec.de>2015-01-27 14:02:09 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2015-01-28 10:02:56 +0100
commitf0f6a7477b09612ba3f57ace321a6641d77b39db (patch)
tree0ad8904c228e27816178382392ecbc312080d6a0 /Documentation/boards
parentf4e1969c19fa80f9f777f8d9c0f9d60202443576 (diff)
downloadbarebox-f0f6a7477b09612ba3f57ace321a6641d77b39db.tar.gz
barebox-f0f6a7477b09612ba3f57ace321a6641d77b39db.tar.xz
Fix spelling: pathes -> paths
Signed-off-by: Wadim Egorov <w.egorov@phytec.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Documentation/boards')
-rw-r--r--Documentation/boards/efi.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index 2147cb63db..b7ad40e472 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -164,20 +164,20 @@ Care must be taken that a partition is only accessed either via the Block IO Pro
the File IO Interface. Doing both at the same time will most likely result in data
corruption on the partition
-EFI device pathes
------------------
+EFI device paths
+----------------
-In EFI each device can be pointed to using a device path. Device pathes have multiple
+In EFI each device can be pointed to using a device path. Device paths have multiple
components. The toplevel component on X86 systems will be the PCI root complex, on
other systems this can be the physical memory space. Each component will now descrive
how to find the child component on the parent bus. Additional device path nodes can
-describe network addresses or filenames on partitions. Device pathes have a binary
+describe network addresses or filenames on partitions. Device paths have a binary
representation and a clearly defined string representation. These characteristics make
-device pathes suitable for describing boot entries. barebox could use device pathes
-to store the reference to kernels on boot media. Also device pathes could be used to
+device paths suitable for describing boot entries. barebox could use device paths
+to store the reference to kernels on boot media. Also device paths could be used to
pass a root filesystem to the Kernel.
-Currently device pathes are only integrated into barebox in a way that each EFI device
+Currently device paths are only integrated into barebox in a way that each EFI device
has a device parameter ``devpath`` which contains its device path:
.. code-block:: sh