Hi Wolfgang,
On 20 September 2017 at 13:55, Wolfgang Denk wrote:
> Dear Simon,
>
> sorry for jumping in so late...
>
> In message <20170916212331.170463-1-...@chromium.org> you wrote:
>>
>> At present U-Boot has a logbuffer feature which records output in a memory
>> buffer for later display or s
Hi Heinrich,
On 20 September 2017 at 14:20, Heinrich Schuchardt wrote:
> On 09/20/2017 04:32 AM, Masahiro Yamada wrote:
>> Hi Simon,
>>
>>
>> 2017-09-17 6:23 GMT+09:00 Simon Glass :
>>> U-Boot currently has fairly rudimentary logging features. A basic printf()
>>> provides console output and debu
On 09/20/2017 04:32 AM, Masahiro Yamada wrote:
> Hi Simon,
>
>
> 2017-09-17 6:23 GMT+09:00 Simon Glass :
>> U-Boot currently has fairly rudimentary logging features. A basic printf()
>> provides console output and debug() provides debug output which is
>> activated if DEBUG is defined in the file
Dear Simon,
sorry for jumping in so late...
In message <20170916212331.170463-1-...@chromium.org> you wrote:
>
> At present U-Boot has a logbuffer feature which records output in a memory
> buffer for later display or storage. This is useful but is not at present
> enabled for any board.
Backgro
Hi Simon,
2017-09-17 6:23 GMT+09:00 Simon Glass :
> U-Boot currently has fairly rudimentary logging features. A basic printf()
> provides console output and debug() provides debug output which is
> activated if DEBUG is defined in the file containing the debug()
> statements.
>
> It would be usef
U-Boot currently has fairly rudimentary logging features. A basic printf()
provides console output and debug() provides debug output which is
activated if DEBUG is defined in the file containing the debug()
statements.
It would be useful to have a few more features:
- control of debug output at r
6 matches
Mail list logo
