colin/u-boot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

global: Use proper project name U-Boot

Browse Source 
Use proper project name in comments, Kconfig, readmes.

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: Michal Simek <michal.simek@amd.com>
Link: https://lore.kernel.org/r/0dbdf0432405c1c38ffca55703b6737a48219e79.1684307818.git.michal.simek@amd.com
This commit is contained in:
Michal Simek
2023-05-17 09:17:16 +02:00
parent 6fe46936a3
commit 1be82afa80
66 changed files with 103 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/develop/driver-model/bind.rst
View File

@@ -7,7 +7,7 @@ Binding/unbinding a driver
This document aims to describe the bind and unbind commands.
For debugging purpose, it should be useful to bind or unbind a driver from
the U-boot command line.
the U-Boot command line.
The unbind command calls the remove device driver callback and unbind the
device from its driver.

6
doc/develop/driver-model/fs_firmware_loader.rst
View File

@@ -92,9 +92,9 @@ For example of getting DT phandle from /chosen and creating instance:
if (ret)
return ret;
Firmware loader driver is also designed to support U-boot environment
Firmware loader driver is also designed to support U-Boot environment
variables, so all these data from FDT can be overwritten
through the U-boot environment variable during run time.
through the U-Boot environment variable during run time.
For examples:
@@ -110,7 +110,7 @@ fw_ubi_volume:
When above environment variables are set, environment values would be
used instead of data from FDT.
The benefit of this design allows user to change storage attribute data
at run time through U-boot console and saving the setting as default
at run time through U-Boot console and saving the setting as default
environment values in the storage for the next power cycle, so no
compilation is required for both driver and FDT.