u-boot.git/doc, branch v2018.03-rc3 Unnamed repository; edit this file 'description' to name the repository. efi_loader: split README.efi into two separate documents 2018-02-09T23:24:00+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2018-01-30T19:03:02+00:00 f3b5056c4e726238f3cbcdb8e5c34f38ba197611 README.efi describes two different concepts: * U-Boot exposing the UEFI API * U-Boot running on top of UEFI. This patch splits the document in two. Religious references are removed. The separation of the concepts makes sense before detailing the internals of U-Boot exposing the UEFI API in a future patch. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: Alexander Graf <agraf@suse.de> 
README.efi describes two different concepts:
* U-Boot exposing the UEFI API
* U-Boot running on top of UEFI.

This patch splits the document in two.
Religious references are removed.

The separation of the concepts makes sense before detailing the internals
of U-Boot exposing the UEFI API in a future patch.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
doc: watchdog: Remove Blackfin related documentation entry 2018-02-08T03:06:19+00:00 Lukasz Majewski lukma@denx.de 2018-02-05T22:42:57+00:00 5030eaa499b17ff74d0420457731522e2d829c7c This commit cleans up the README.watchdog by removing the reminescent of ADI's Blackfin architecture removed some time ago. Signed-off-by: Lukasz Majewski <lukma@denx.de> 
This commit cleans up the README.watchdog by removing the reminescent of
ADI's Blackfin architecture removed some time ago.

Signed-off-by: Lukasz Majewski <lukma@denx.de>
Merge git://git.denx.de/u-boot-dm 2018-02-04T13:30:31+00:00 Tom Rini trini@konsulko.com 2018-02-04T13:30:31+00:00 211a3a23b92798e870b85262ef07265845813a6c 






doc: mxc_hab: Improve the config option list
2018-02-04T11:14:10+00:00

Fabio Estevam
fabio.estevam@nxp.com

2018-01-21T17:57:32+00:00

79d08029534c6e43905d410c5804cc2fb9984399

The original text is from the time that the config options were not
converted to Kconfig.

After the conversion to Kconfig only CONFIG_SECURE_BOOT and
CONFIG_CMD_DEKBLOB need to be selected by the user.

The other config options are automatically selected by the Kconfig
logic.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Reviewed-by: Breno Lima <breno.lima@nxp.com>





The original text is from the time that the config options were not
converted to Kconfig.

After the conversion to Kconfig only CONFIG_SECURE_BOOT and
CONFIG_CMD_DEKBLOB need to be selected by the user.

The other config options are automatically selected by the Kconfig
logic.

Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Reviewed-by: Breno Lima <breno.lima@nxp.com>







log: add category LOGC_EFI
2018-02-03T17:09:28+00:00

Heinrich Schuchardt
xypron.glpk@gmx.de

2018-01-22T19:10:45+00:00

1973b381a1b3545783c3238080f566746579e923

The EFI implementation does not fit into any of the existing categories.

Provide LOGC_EFI so that EFI related message can be filtered.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>





The EFI implementation does not fit into any of the existing categories.

Provide LOGC_EFI so that EFI related message can be filtered.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>







log: Add a way to log error-return values
2018-02-03T17:09:27+00:00

Simon Glass
sjg@chromium.org

2017-12-28T20:14:23+00:00

3707c6ee0d1f939130a62c945b56045d9a83fafc

When functions return an error it propagates up the stack to the point
where it is reported. Often the error code provides enough information
about the root cause of the error that this is obvious what went wrong.

However in some cases the error may be hard to trace. For example if a
driver uses several devices to perform an operation, it may not be
obvious which one failed.

Add a log_ret() macro to help with this. This can be used to wrap any
error-return value. The logging system will then output a log record when
the original error is generated, making it easy to trace the call stack
of the error.

This macro can significantly impact code size, so its use is controlled
by a Kconfig option, which is enabled for sandbox.

Signed-off-by: Simon Glass <sjg@chromium.org>





When functions return an error it propagates up the stack to the point
where it is reported. Often the error code provides enough information
about the root cause of the error that this is obvious what went wrong.

However in some cases the error may be hard to trace. For example if a
driver uses several devices to perform an operation, it may not be
obvious which one failed.

Add a log_ret() macro to help with this. This can be used to wrap any
error-return value. The logging system will then output a log record when
the original error is generated, making it easy to trace the call stack
of the error.

This macro can significantly impact code size, so its use is controlled
by a Kconfig option, which is enabled for sandbox.

Signed-off-by: Simon Glass <sjg@chromium.org>







log: Add documentation for commands and formatting
2018-02-03T17:09:27+00:00

Simon Glass
sjg@chromium.org

2017-12-28T20:14:22+00:00

8cb7c04248c9f0c3b79325b82844d79a680ef2eb

Add some notes about recent new features.

Signed-off-by: Simon Glass <sjg@chromium.org>





Add some notes about recent new features.

Signed-off-by: Simon Glass <sjg@chromium.org>







Merge tag 'xilinx-for-v2018.03' of git://git.denx.de/u-boot-microblaze
2018-01-31T12:10:55+00:00

Tom Rini
trini@konsulko.com

2018-01-31T12:10:55+00:00

ab21ecef7a38dd211fe6db35c6e60800445eb6a2

Xilinx changes for v2018.03

- Several Kconfig fixes (also moving configs to defconfigs)
- Some DTS updates
- ZynqMP psu rework based on Zynq concept
- Add low level initialization for zc770 and zcu102
- Add support for Zynq zc770 x16 nand configuration
- Add mini nand/emmc ZynqMP targets
- Some arasan nand changes





Xilinx changes for v2018.03

- Several Kconfig fixes (also moving configs to defconfigs)
- Some DTS updates
- ZynqMP psu rework based on Zynq concept
- Add low level initialization for zc770 and zcu102
- Add support for Zynq zc770 x16 nand configuration
- Add mini nand/emmc ZynqMP targets
- Some arasan nand changes







doc: zynq: Describe status of zc770-xm011
2018-01-30T13:28:19+00:00

Michal Simek
michal.simek@xilinx.com

2018-01-15T06:38:21+00:00

546a496ffd72a943a80cc0bfbbdb53fc5eec2a5f

zc770-xm011 is also added and supported. Reflect this in README.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>





zc770-xm011 is also added and supported. Reflect this in README.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>







efi_loader: add a README.iscsi describing booting via iSCSI
2018-01-28T20:37:13+00:00

Heinrich Schuchardt
xypron.glpk@gmx.de

2018-01-28T14:26:02+00:00

29a8a2828e5c6f3f167a8526a80da992b4626daf

The appended README explains how U-Boot and iPXE can be used
to boot a diskless system from an iSCSI SAN.

The maintainer for README.efi and README.iscsi is set.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
[agraf: s/Adress/Address/]
Signed-off-by: Alexander Graf <agraf@suse.de>





The appended README explains how U-Boot and iPXE can be used
to boot a diskless system from an iSCSI SAN.

The maintainer for README.efi and README.iscsi is set.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
[agraf: s/Adress/Address/]
Signed-off-by: Alexander Graf <agraf@suse.de>