sysmo-bts
/
barebox
9
0
Fork 0
Code Releases Activity

Fix spelling: pathes -> paths 

Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
This commit is contained in:
Wadim Egorov 2015-01-27 14:02:09 +01:00 committed by Sascha Hauer
parent f4e1969c19
commit f0f6a7477b
9 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Documentation/boards/efi.rst
View File

@ -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 the File IO Interface. Doing both at the same time will most likely result in data
corruption on the partition 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 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 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 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 representation and a clearly defined string representation. These characteristics make
device pathes suitable for describing boot entries. barebox could use device pathes device paths suitable for describing boot entries. barebox could use device paths
to store the reference to kernels on boot media. Also device pathes could be used to to store the reference to kernels on boot media. Also device paths could be used to
pass a root filesystem to the Kernel. 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: has a device parameter ``devpath`` which contains its device path:
.. code-block:: sh .. code-block:: sh

4
Documentation/user/booting-linux.rst
View File

@ -166,7 +166,7 @@ A Bootloader Spec Entry consists of key value pairs::
linux /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/linux linux /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/linux
initrd /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/initrd initrd /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/initrd
All pathes are absolute pathes in the partition. Bootloader Spec Entries can All paths are absolute paths in the partition. Bootloader Spec Entries can
be created manually, but there also is the ``scripts/kernel-install`` tool to be created manually, but there also is the ``scripts/kernel-install`` tool to
create/list/modify entries directly on a MMC/SD card or other media. To use create/list/modify entries directly on a MMC/SD card or other media. To use
it create a SD card / USB memory stick with a /boot partition with type 0xea. it create a SD card / USB memory stick with a /boot partition with type 0xea.
@ -246,7 +246,7 @@ link target is exported from the server.
``boot net`` will then start the Kernel. ``boot net`` will then start the Kernel.
If the pathes or names are not suitable they can be adjusted in If the paths or names are not suitable they can be adjusted in
``/env/boot/net``: ``/env/boot/net``:
.. code-block:: sh .. code-block:: sh

2
Documentation/user/variables.rst
View File

@ -79,7 +79,7 @@ of all variables with special meaning along with a short description::
barebox:/ magicvar barebox:/ magicvar
OPTARG optarg for hush builtin getopt OPTARG optarg for hush builtin getopt
PATH colon separated list of pathes to search for executables PATH colon separated list of paths to search for executables
PS1 hush prompt PS1 hush prompt
armlinux_architecture ARM machine ID armlinux_architecture ARM machine ID
armlinux_system_rev ARM system revision armlinux_system_rev ARM system revision

2
commands/Kconfig
View File

@ -2018,7 +2018,7 @@ config CMD_OF_PROPERTY
Valid formats for values: Valid formats for values:
<0x00112233 4 05> - an array of cells. cells not beginning with a digit are <0x00112233 4 05> - an array of cells. cells not beginning with a digit are
interpreted as node pathes and converted to phandles interpreted as node paths and converted to phandles
[00 11 22 .. nn] - byte stream [00 11 22 .. nn] - byte stream
If the value does not start with '<' or '[' it is interpreted as string If the value does not start with '<' or '[' it is interpreted as string

2
commands/of_property.c
View File

@ -308,7 +308,7 @@ BAREBOX_CMD_HELP_OPT ("-d", "delete property")
BAREBOX_CMD_HELP_TEXT("") BAREBOX_CMD_HELP_TEXT("")
BAREBOX_CMD_HELP_TEXT("Valid formats for values:") BAREBOX_CMD_HELP_TEXT("Valid formats for values:")
BAREBOX_CMD_HELP_TEXT("<0x00112233 4 05> - an array of cells. cells not beginning with a digit are") BAREBOX_CMD_HELP_TEXT("<0x00112233 4 05> - an array of cells. cells not beginning with a digit are")
BAREBOX_CMD_HELP_TEXT(" interpreted as node pathes and converted to phandles") BAREBOX_CMD_HELP_TEXT(" interpreted as node paths and converted to phandles")
BAREBOX_CMD_HELP_TEXT("[00 11 22 .. nn] - byte stream") BAREBOX_CMD_HELP_TEXT("[00 11 22 .. nn] - byte stream")
BAREBOX_CMD_HELP_TEXT("If the value does not start with '<' or '[' it is interpreted as string") BAREBOX_CMD_HELP_TEXT("If the value does not start with '<' or '[' it is interpreted as string")
BAREBOX_CMD_HELP_END BAREBOX_CMD_HELP_END

6
common/Kconfig
View File

@ -674,9 +674,9 @@ config DEFAULT_ENVIRONMENT_PATH
depends on DEFAULT_ENVIRONMENT depends on DEFAULT_ENVIRONMENT
prompt "Default environment path" prompt "Default environment path"
help help
Space separated list of pathes the default environment will be taken from. Space separated list of paths the default environment will be taken from.
Relative pathes will be relative to the barebox Toplevel dir, but absolute Relative paths will be relative to the barebox Toplevel dir, but absolute
pathes are fine aswell. paths are fine aswell.
config BAREBOXENV_TARGET config BAREBOXENV_TARGET
bool bool

2
common/hush.c
View File

@ -2020,7 +2020,7 @@ BAREBOX_CMD_START(getopt)
BAREBOX_CMD_END BAREBOX_CMD_END
#endif #endif
BAREBOX_MAGICVAR(PATH, "colon separated list of pathes to search for executables"); BAREBOX_MAGICVAR(PATH, "colon separated list of paths to search for executables");
#ifdef CONFIG_HUSH_FANCY_PROMPT #ifdef CONFIG_HUSH_FANCY_PROMPT
BAREBOX_MAGICVAR(PS1, "hush prompt"); BAREBOX_MAGICVAR(PS1, "hush prompt");
#endif #endif

2
drivers/of/of_path.c
View File

@ -113,7 +113,7 @@ out:
* @outpath: if this function returns 0 outpath will contain the path belonging * @outpath: if this function returns 0 outpath will contain the path belonging
* to the input path description. Must be freed with free(). * to the input path description. Must be freed with free().
* *
* pathes in the devicetree have the form of a multistring property. The first * paths in the devicetree have the form of a multistring property. The first
* string contains the full path to the physical device containing the path. * string contains the full path to the physical device containing the path.
* The remaining strings have the form "<type>:<options>". Currently supported * The remaining strings have the form "<type>:<options>". Currently supported
* for <type> are: * for <type> are:

4
scripts/genenv
View File

@ -2,8 +2,8 @@
# Generate the default environment file from a list of directories # Generate the default environment file from a list of directories
# usage: genenv <basedir> <objdir> <target> <dir>... # usage: genenv <basedir> <objdir> <target> <dir>...
# where <basedir> is the base directory for relative pathes in <dir> # where <basedir> is the base directory for relative paths in <dir>
# where <objdir> is the base directory for relative pathes for result # where <objdir> is the base directory for relative paths for result
# and <target> is the resulting binary environment # and <target> is the resulting binary environment
objtree=$2 objtree=$2
basedir=$1 basedir=$1