History log of /openbmc/u-boot/doc/README.log (Results 1 – 9 of 9)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v00.04.15, v00.04.14, v00.04.13, v00.04.12, v00.04.11, v00.04.10, v00.04.09, v00.04.08, v00.04.07, v00.04.06, v00.04.05, v00.04.04, v00.04.03, v00.04.02, v00.04.01, v00.04.00, v2021.04, v00.03.03, v2021.01, v2020.10, v2020.07, v00.02.13, v2020.04, v2020.01, v2019.10, v00.02.05, v00.02.04, v00.02.03, v00.02.02, v00.02.01, v2019.07, v00.02.00, v2019.04
# 0c41e59a 20-Feb-2019 Tom Rini <trini@konsulko.com>

Merge git://git.denx.de/u-boot-x86

- Add support for sound.

Albeit the big changeset, changes are pretty limited to x86 only and a
few new sound drivers used by x86 so I think it would be good to h

Merge git://git.denx.de/u-boot-x86

- Add support for sound.

Albeit the big changeset, changes are pretty limited to x86 only and a
few new sound drivers used by x86 so I think it would be good to have
this in the next release.

show more ...


# f9811e85 16-Feb-2019 Simon Glass <sjg@chromium.org>

log: Allow #define LOG_DEBUG to enable logging in a file

At present it is possible to '#define DEBUG' at the top of a file which
causes all debug() statements in that file to become active. There is

log: Allow #define LOG_DEBUG to enable logging in a file

At present it is possible to '#define DEBUG' at the top of a file which
causes all debug() statements in that file to become active. There is
currently no equivalent with logging, but this is a useful function.

Add a LOG_DEBUG define along with documentation.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

show more ...


# 8dee7b96 16-Feb-2019 Simon Glass <sjg@chromium.org>

log: Add documentation for convenience functions

The log_debug(), etc. function are documented only in the header file at
present. Add a section to README.log also.

Signed-off-by: Simon Glass <sjg@

log: Add documentation for convenience functions

The log_debug(), etc. function are documented only in the header file at
present. Add a section to README.log also.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

show more ...


Revision tags: v2018.07
# b71ac160 02-Apr-2018 Simon Glass <sjg@chromium.org>

log: Add units to code-size stats in README.log

Without the units these numbers are confusing. Add a comment about the
unit being 'bytes' and mention 'buildman' as the source.

Suggested-by: Lukasz

log: Add units to code-size stats in README.log

Without the units these numbers are confusing. Add a comment about the
unit being 'bytes' and mention 'buildman' as the source.

Suggested-by: Lukasz Majewski <lukma@denx.de>
Signed-off-by: Simon Glass <sjg@chromium.org>

show more ...


Revision tags: v2018.03
# 211a3a23 04-Feb-2018 Tom Rini <trini@konsulko.com>

Merge git://git.denx.de/u-boot-dm


# 1973b381 22-Jan-2018 Heinrich Schuchardt <xypron.glpk@gmx.de>

log: add category LOGC_EFI

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

log: add category LOGC_EFI

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>

show more ...


Revision tags: v2018.01
# 3707c6ee 28-Dec-2017 Simon Glass <sjg@chromium.org>

log: Add a way to log error-return values

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

log: Add a way to log error-return values

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>

show more ...


# 8cb7c042 28-Dec-2017 Simon Glass <sjg@chromium.org>

log: Add documentation for commands and formatting

Add some notes about recent new features.

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


# 1d0f30a8 04-Dec-2017 Simon Glass <sjg@chromium.org>

log: Add documentation

Add documentation for the log system.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>